Events Sales Manager
for each section heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include only sections with real specific content. Must preserve all substantive info. No invented or summarized away detail. Avoid filler like "commensurate with experience". Must not create sections unless posting actually states them.
We need to parse the posting for content.
Let's extract sections:
- About the role: The posting includes description of Workbox and role overview: "Workbox is a national workspace operator... We are seeking a full-time Events Sales Manager to join our events team. This role will serve as the primary operational partner to the Director of Events and will take ownership of event coordination after a booking is signed and paid, while also carrying a defined sales and revenue responsibility. The ideal candidate is highly organized, client-focused, comfortable in a sales environment, and able to manage numerous operational details while delivering exceptional event experiences. Operationally, this position will be based in Chicago and will provide regular on-site event coverage across Workbox's Chicago locations. From a sales perspective, the role will support meeting room and select event sales nationally. This position requires an on-site presence Monday through Friday during standard business hours (8 am to 5 pm), with the flexibility to support evening events and fulfill additional event-related responsibilities as needed."
That's about role. Could be "About the role". We'll put prose.
- Responsibilities: The posting includes sections: "Role Structure & Collaboration", "Event Coordination & Client Ownership", "Day-of Event Execution", "Sales & Revenue Responsibilities", "Property Management & Vendor Partnerships", "Operational Support & Department Organization". Those are responsibilities. We'll combine into a list under Responsibilities.
- Requirements: The posting includes "Requirements" bullet list: "2 - 3 years of experience in events, hospitality, sales, customer service, venue operations, or a related client-facing role", "Bachelor's degree in Hospitality Management, Event Management, Business Administration, Communications, or a related field", "Strong customer service, written communication, and verbal communication skills", "Highly organized with strong attention to detail and the ability to manage multiple events, deadlines, and priorities at the same time", "Comfortable balancing operational responsibilities with sales activity and revenue expectations", "Confident communicating with clients, property management teams, vendors, and internal stakeholders", "Ability to take ownership, make sound day-to-day decisions, and escalate issues appropriately", "Working in CRM platforms and maintaining accurate records and reporting", "Hands-on approach and willingness to actively support event setup, execution, troubleshooting, and breakdown activities", "Flexibility to work evening events as needed. Weekend availability may be required in the future if Workbox expands weekend event operations". We'll list these as
- .
- Qualifications: The posting doesn't have a separate "Qualifications" heading; the requirements may be considered qualifications. But we have a "Requirements" section already. Should we also have "Qualifications"? The instruction says use headings only when posting has real specific content. There's no separate "Qualifications" heading; we could combine qualifications into Requirements or maybe we can treat the degree and experience as qualifications. But we already have Requirements. To avoid duplication, we might not create a Qualifications section if content overlaps. However the instruction says we can have sections like Qualifications if there is content. The posting includes "Requirements" which likely covers qualifications. We could still have a Qualifications section with the degree and experience, but that would duplicate. Better to follow the posting: they have a "Requirements" heading. So we will output a section with heading
Requirements
. Not also Qualifications.
- Skills: The posting includes skills embedded in requirements; but there is no separate Skills heading. Could we create a Skills section? The instruction: include a section ONLY when the posting has real, specific content for it. There's no explicit Skills heading, but we could infer skills from responsibilities. However better not to create a Skills section unless explicitly present. The posting does not have a "Skills" heading. So we skip.
- Benefits: The posting includes "Benefits" heading with list: "Annual base salary of $55,000 - $60,000, plus event sales commission", "Comprehensive health benefits, including medical, dental and vision coverage", "Company-paid life insurance", "401(k) plan", "Generous PTO", "FSA, HSA and commuter benefits", "Ongoing training and professional development". We'll output Benefits section with list.
- Pay: The posting includes salary info inside Benefits. There's no separate Pay heading. Should we create Pay? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Since Pay is not a separate heading, we should not create a Pay section. The salary info is within Benefits. So we keep it in Benefits.
- Schedule: The posting includes schedule info: "This position requires an on-site presence Monday through Friday during standard business hours (8 am to 5 pm), with the flexibility to support evening events and fulfill additional event-related responsibilities as needed." That's schedule. There's no explicit Schedule heading, but we have schedule info. Should we create a Schedule section? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not say we must only use headings that appear; we can create sections if content exists. However they gave list of possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create a Schedule section if we have schedule content. The posting does have schedule details. So we should include a Schedule section.
But we must avoid duplication: schedule info also appears in About the role paragraph. We could move schedule details to Schedule section and remove from About the role to avoid duplication. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We can keep schedule info in both places? That would be duplication but not invented. It's okay to repeat? Might be considered redundant but not violating. However better to avoid duplication by moving schedule details to Schedule section and adjust About the role to not include schedule specifics. But we must preserve all info; moving is fine as long as we keep it somewhere.
Thus we will have sections: About the role (overview without schedule), Responsibilities (list), Requirements (list), Benefits (list), Schedule (paragraph). Possibly also Qualifications? Not needed.
Now we need to format.
About the role: prose summarizing Workbox and role overview excluding schedule. Let's craft:
"Workbox is a national workspace operator that goes beyond coworking—our ecosystem accelerates ambition, cultivates connections, and helps businesses thrive. In addition to office space and coworking solutions, we offer connection to a network of investors, professional specialists, and high growth businesses across our entire portfolio. Our workspace products include private offices, reserved desks and floating memberships, as well as meeting rooms and event spaces. We currently operate 13 locations, encompassing over 400,000 square feet, in seven cities across the U.S., and our differentiation has led to us being one of the fastest growing workspace operators in the country. We are seeking a full-time Events Sales Manager to join our events team. This role will serve as the primary operational partner to the Director of Events and will take ownership of event coordination after a booking is signed and paid, while also carrying a defined sales and revenue responsibility. The ideal candidate is highly organized, client-focused, comfortable in a sales environment, and able to manage numerous operational details while delivering exceptional event experiences. Operationally, this position will be based in Chicago and will provide regular on-site event coverage across Workbox's Chicago locations. From a sales perspective, the role will support meeting room and select event sales nationally."
That's about role.
Responsibilities: we need to list duties from the subsections.
Let's extract bullet points:
From Role Structure & Collaboration:
- Report primarily to the Director of Events for event operations, coordination, execution, and day-to-day priorities
- Partner with the VP of Sales on revenue performance and sales goals
- Work closely with local and regional team members, Marketing, property management teams, and external vendors to ensure events are properly coordinated and executed
- Operate as an extension of the Director of Events, while maintaining clear ownership of assigned responsibilities and client communication
Event Coordination & Client Ownership:
- Take ownership of event coordination once an event is signed and paid, becoming the primary client contact from handoff through event execution
- Manage all final event details including timelines, room and floor-plan setup, catering coordination, AV needs, guest lists, certificates of insurance, building access, vendor arrival, and final client confirmations
- Coordinate post-booking event modifications, including additional time, services, or other approved adjustments
- Maintain event checklists, documentation, calendars, client templates, venue information, and other operational tools in partnership with the Director of Events
- Ensure event and sales data are accurately recorded and maintained within CRM platforms and other internal systems
- Support post-event information gathering, including client feedback, review opportunities, and repeat-business opportunities in partnership with the Director of Events
- Keep the Director of Events informed and included where appropriate, while independently managing routine client questions and coordination needs
Day-of Event Execution:
- Provide regular on-site coverage for Chicago events, including evening events when required
- Support physical event setup and breakdown, client arrival, vendor coordination, troubleshooting, guest experience, and overall event execution
- Coordinate with the Director of Events on staffing plans when multiple events occur simultaneously, including collaborating with Community Associates when additional coverage is needed
- Serve as a dependable on-site point of contact for clients, vendors, building teams, and internal staff throughout the event
Sales & Revenue Responsibilities:
- Own meeting room vertical within the Events department
- Respond to inbound meeting room inquiries, qualify client needs, provide options and pricing, conduct follow-up, and move opportunities through booking
- Maintain an active sales pipeline, accurate CRM activity, timely follow-up, and clear next steps on all owned opportunities
- Provide sales coverage and support for the Director of Events when needed
Property Management & Vendor Partnerships:
- Build and maintain strong working relationships with property management teams across all event locations
- Coordinate all building-related event requirements, including security, freight elevators, loading access, HVAC, cleaning, after-hours access, vendor access, and other building-specific procedures
- Serve as the primary liaison with property management, ensuring all event requirements are communicated, scheduled, confirmed, and executed seamlessly
- Establish and maintain relationships with preferred vendors including caterers, AV providers, décor companies, rental partners, and other event service providers
- Identify and onboard new vendor relationships when needed, while maintaining an organized preferred-vendor list in partnership with the Director of Events
Operational Support & Department Organization:
- Maintain event calendars, venue information, event supplies and inventory, vendor lists, standard operating procedures, and other department resources in partnership with the Director of Events
- Help identify operational gaps, recurring event issues, or process improvements and recommend practical solutions
We'll put these as - items.
Requirements: list as earlier.
Benefits: list.
Schedule: paragraph: "This position requires an on-site presence Monday through Friday during standard business hours (8 am to 5 pm), with the flexibility to support evening events and fulfill additional event-related responsibilities as needed."
Now output HTML fragment: only the sections, each with
heading then content.
We must not include or . Just the fragment.
Let's craft.
Be careful to escape any HTML special characters? Not needed.
We'll produce:
About the role
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include only sections with real specific content. Must preserve all substantive info. No invented or summarized away detail. Avoid filler like "commensurate with experience". Must not create sections unless posting actually states them. We need to parse the posting for content. Let's extract sections: - About the role: The posting includes description of Workbox and role overview: "Workbox is a national workspace operator... We are seeking a full-time Events Sales Manager to join our events team. This role will serve as the primary operational partner to the Director of Events and will take ownership of event coordination after a booking is signed and paid, while also carrying a defined sales and revenue responsibility. The ideal candidate is highly organized, client-focused, comfortable in a sales environment, and able to manage numerous operational details while delivering exceptional event experiences. Operationally, this position will be based in Chicago and will provide regular on-site event coverage across Workbox's Chicago locations. From a sales perspective, the role will support meeting room and select event sales nationally. This position requires an on-site presence Monday through Friday during standard business hours (8 am to 5 pm), with the flexibility to support evening events and fulfill additional event-related responsibilities as needed." That's about role. Could be "About the role". We'll put prose. - Responsibilities: The posting includes sections: "Role Structure & Collaboration", "Event Coordination & Client Ownership", "Day-of Event Execution", "Sales & Revenue Responsibilities", "Property Management & Vendor Partnerships", "Operational Support & Department Organization". Those are responsibilities. We'll combine into a list under Responsibilities. - Requirements: The posting includes "Requirements" bullet list: "2 - 3 years of experience in events, hospitality, sales, customer service, venue operations, or a related client-facing role", "Bachelor's degree in Hospitality Management, Event Management, Business Administration, Communications, or a related field", "Strong customer service, written communication, and verbal communication skills", "Highly organized with strong attention to detail and the ability to manage multiple events, deadlines, and priorities at the same time", "Comfortable balancing operational responsibilities with sales activity and revenue expectations", "Confident communicating with clients, property management teams, vendors, and internal stakeholders", "Ability to take ownership, make sound day-to-day decisions, and escalate issues appropriately", "Working in CRM platforms and maintaining accurate records and reporting", "Hands-on approach and willingness to actively support event setup, execution, troubleshooting, and breakdown activities", "Flexibility to work evening events as needed. Weekend availability may be required in the future if Workbox expands weekend event operations". We'll list these as
- .
- Qualifications: The posting doesn't have a separate "Qualifications" heading; the requirements may be considered qualifications. But we have a "Requirements" section already. Should we also have "Qualifications"? The instruction says use headings only when posting has real specific content. There's no separate "Qualifications" heading; we could combine qualifications into Requirements or maybe we can treat the degree and experience as qualifications. But we already have Requirements. To avoid duplication, we might not create a Qualifications section if content overlaps. However the instruction says we can have sections like Qualifications if there is content. The posting includes "Requirements" which likely covers qualifications. We could still have a Qualifications section with the degree and experience, but that would duplicate. Better to follow the posting: they have a "Requirements" heading. So we will output a section with heading
Requirements
. Not also Qualifications. - Skills: The posting includes skills embedded in requirements; but there is no separate Skills heading. Could we create a Skills section? The instruction: include a section ONLY when the posting has real, specific content for it. There's no explicit Skills heading, but we could infer skills from responsibilities. However better not to create a Skills section unless explicitly present. The posting does not have a "Skills" heading. So we skip. - Benefits: The posting includes "Benefits" heading with list: "Annual base salary of $55,000 - $60,000, plus event sales commission", "Comprehensive health benefits, including medical, dental and vision coverage", "Company-paid life insurance", "401(k) plan", "Generous PTO", "FSA, HSA and commuter benefits", "Ongoing training and professional development". We'll output Benefits section with list. - Pay: The posting includes salary info inside Benefits. There's no separate Pay heading. Should we create Pay? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Since Pay is not a separate heading, we should not create a Pay section. The salary info is within Benefits. So we keep it in Benefits. - Schedule: The posting includes schedule info: "This position requires an on-site presence Monday through Friday during standard business hours (8 am to 5 pm), with the flexibility to support evening events and fulfill additional event-related responsibilities as needed." That's schedule. There's no explicit Schedule heading, but we have schedule info. Should we create a Schedule section? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not say we must only use headings that appear; we can create sections if content exists. However they gave list of possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create a Schedule section if we have schedule content. The posting does have schedule details. So we should include a Schedule section. But we must avoid duplication: schedule info also appears in About the role paragraph. We could move schedule details to Schedule section and remove from About the role to avoid duplication. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We can keep schedule info in both places? That would be duplication but not invented. It's okay to repeat? Might be considered redundant but not violating. However better to avoid duplication by moving schedule details to Schedule section and adjust About the role to not include schedule specifics. But we must preserve all info; moving is fine as long as we keep it somewhere. Thus we will have sections: About the role (overview without schedule), Responsibilities (list), Requirements (list), Benefits (list), Schedule (paragraph). Possibly also Qualifications? Not needed. Now we need to format. About the role: prose summarizing Workbox and role overview excluding schedule. Let's craft: "Workbox is a national workspace operator that goes beyond coworking—our ecosystem accelerates ambition, cultivates connections, and helps businesses thrive. In addition to office space and coworking solutions, we offer connection to a network of investors, professional specialists, and high growth businesses across our entire portfolio. Our workspace products include private offices, reserved desks and floating memberships, as well as meeting rooms and event spaces. We currently operate 13 locations, encompassing over 400,000 square feet, in seven cities across the U.S., and our differentiation has led to us being one of the fastest growing workspace operators in the country. We are seeking a full-time Events Sales Manager to join our events team. This role will serve as the primary operational partner to the Director of Events and will take ownership of event coordination after a booking is signed and paid, while also carrying a defined sales and revenue responsibility. The ideal candidate is highly organized, client-focused, comfortable in a sales environment, and able to manage numerous operational details while delivering exceptional event experiences. Operationally, this position will be based in Chicago and will provide regular on-site event coverage across Workbox's Chicago locations. From a sales perspective, the role will support meeting room and select event sales nationally." That's about role. Responsibilities: we need to list duties from the subsections. Let's extract bullet points: From Role Structure & Collaboration: - Report primarily to the Director of Events for event operations, coordination, execution, and day-to-day priorities - Partner with the VP of Sales on revenue performance and sales goals - Work closely with local and regional team members, Marketing, property management teams, and external vendors to ensure events are properly coordinated and executed - Operate as an extension of the Director of Events, while maintaining clear ownership of assigned responsibilities and client communication Event Coordination & Client Ownership: - Take ownership of event coordination once an event is signed and paid, becoming the primary client contact from handoff through event execution - Manage all final event details including timelines, room and floor-plan setup, catering coordination, AV needs, guest lists, certificates of insurance, building access, vendor arrival, and final client confirmations - Coordinate post-booking event modifications, including additional time, services, or other approved adjustments - Maintain event checklists, documentation, calendars, client templates, venue information, and other operational tools in partnership with the Director of Events - Ensure event and sales data are accurately recorded and maintained within CRM platforms and other internal systems - Support post-event information gathering, including client feedback, review opportunities, and repeat-business opportunities in partnership with the Director of Events - Keep the Director of Events informed and included where appropriate, while independently managing routine client questions and coordination needs Day-of Event Execution: - Provide regular on-site coverage for Chicago events, including evening events when required - Support physical event setup and breakdown, client arrival, vendor coordination, troubleshooting, guest experience, and overall event execution - Coordinate with the Director of Events on staffing plans when multiple events occur simultaneously, including collaborating with Community Associates when additional coverage is needed - Serve as a dependable on-site point of contact for clients, vendors, building teams, and internal staff throughout the event Sales & Revenue Responsibilities: - Own meeting room vertical within the Events department - Respond to inbound meeting room inquiries, qualify client needs, provide options and pricing, conduct follow-up, and move opportunities through booking - Maintain an active sales pipeline, accurate CRM activity, timely follow-up, and clear next steps on all owned opportunities - Provide sales coverage and support for the Director of Events when needed Property Management & Vendor Partnerships: - Build and maintain strong working relationships with property management teams across all event locations - Coordinate all building-related event requirements, including security, freight elevators, loading access, HVAC, cleaning, after-hours access, vendor access, and other building-specific procedures - Serve as the primary liaison with property management, ensuring all event requirements are communicated, scheduled, confirmed, and executed seamlessly - Establish and maintain relationships with preferred vendors including caterers, AV providers, décor companies, rental partners, and other event service providers - Identify and onboard new vendor relationships when needed, while maintaining an organized preferred-vendor list in partnership with the Director of Events Operational Support & Department Organization: - Maintain event calendars, venue information, event supplies and inventory, vendor lists, standard operating procedures, and other department resources in partnership with the Director of Events - Help identify operational gaps, recurring event issues, or process improvements and recommend practical solutions We'll put these as
- items.
Requirements: list as earlier.
Benefits: list.
Schedule: paragraph: "This position requires an on-site presence Monday through Friday during standard business hours (8 am to 5 pm), with the flexibility to support evening events and fulfill additional event-related responsibilities as needed."
Now output HTML fragment: only the sections, each with
heading then content. We must not include or . Just the fragment. Let's craft. Be careful to escape any HTML special characters? Not needed. We'll produce:
About the role
- items.
Requirements: list as earlier.
Benefits: list.
Schedule: paragraph: "This position requires an on-site presence Monday through Friday during standard business hours (8 am to 5 pm), with the flexibility to support evening events and fulfill additional event-related responsibilities as needed."
Now output HTML fragment: only the sections, each with