How to get speakers to help promote your paid conference

You've confirmed the speakers, published the agenda and opened ticket sales. Now you need the people on that agenda to introduce it to likely attendees. You send an announcement they can share, and a few do. Others forget, ask for different wording or never reply. Meanwhile, you're still responsible for filling the conference.

Speaker event promotion works best when you agree on a small, useful contribution early, connect it to the speaker's subject and handle the preparation yourself. Ask them to explain why their session matters to the people they already reach. Then make sure those people can understand the conference, check the price and buy the right ticket without starting their research again.

That sounds straightforward, but there are several decisions inside it. What can you reasonably ask for? Who needs employer approval? When does a session announcement help someone decide to attend? And how do you measure the result without treating a speaker's reputation as a ticket quota? Let's walk through the process, including the messages you can adapt for your own conference.

Decide what you need speakers to help with

Start with the commercial problem. Perhaps practitioners understand your conference, but their managers don't see why they should pay for it. Perhaps your ticket page has plenty of visitors, but nobody understands the practical value of the programme. Or perhaps you're launching in a new city and need relevant people to hear about you in the first place.

Those problems call for different contributions. A speaker explaining what attendees will work through can help you make the programme clearer. A speaker introducing the conference to a professional community can help you reach potential buyers. A speaker sharing a useful session summary can help attendees explain the purchase to their manager. Decide which job you're asking them to do before writing the request.

Imagine a paid conference for people managing small customer support teams. One session covers organising support during a product launch. A speaker who regularly discusses that problem with working team leaders might reach exactly the right people. Someone with a much larger audience of aspiring founders might generate more attention while reaching fewer people who can justify buying a ticket.

Use that distinction when choosing who to approach first. Read what speakers discuss publicly, ask which communities they participate in and check whether their followers are likely to attend your format and location. You don't need access to their private audience data. You're trying to understand where a relevant invitation would be welcome, including whether their audience has any realistic reason to travel.

Keep responsibility for ticket sales with your conference team. The speaker can make an introduction or explain the content, but you control the offer, price, event page and follow-up. Their contribution should support your wider campaign. If your conference still lacks a clear reason to attend, asking every speaker to post more often will make that problem more visible.

Agree on promotion before it becomes urgent

Raise promotion while you're confirming the speaking arrangement. Explain the audience, the session and the kind of help you're hoping for. A reasonable starting request might be an announcement on a channel they already use, followed by a session preview when the programme is ready. That's a proposed arrangement for discussion, rather than an obligation every speaker automatically accepts.

The useful question is, "What would you feel comfortable sharing with your audience?" You might learn that the speaker avoids promotional posts but welcomes a technical discussion. Another may have a newsletter, yet only mention events in a monthly roundup. Someone else may need their communications team to approve anything using their employer's name. Those answers let you plan around actual availability.

If you've already confirmed the speaker, make the request without pretending it was part of the original agreement. Explain what you'd like, when you need it and that they can decline or suggest something else. Late surprises create unnecessary friction, especially when a speaker accepted an unpaid invitation and is already spending time preparing a session and arranging travel.

Where promotion is a paid contractual deliverable, describe it clearly in the agreement. Specify the channel, approximate timing, approval process and permitted reuse. Distinguish payment for speaking from payment for promotional work so both parties understand the arrangement. Agree what happens if the session changes or the conference is cancelled. Get appropriate advice for the contract and markets involved.

Don't quietly add a requirement to sell tickets. A speaker cannot control whether followers can afford your conference, secure time off or travel to it. If someone separately agrees to a sales commission arrangement, that needs its own terms and disclosure review. Our guide to building an event ambassador programme explains a different kind of ongoing promotional relationship.

For your first request, a message like this is enough: "We're preparing the announcement for your support operations session. Would you be comfortable sharing a short introduction on LinkedIn during the announcement week? We'll send the confirmed details and draft wording for you to edit. If another format suits you better, let me know and we'll work around that."

Make the invitation useful to the speaker's audience

People follow a speaker because they care about the speaker's work, opinions or experience. Your conference announcement should connect to that reason. A generic "Excited to be speaking" post can communicate the appearance, but it leaves potential attendees to work out whether the session will help them. Prepare something that explains the problem and the contribution the speaker will make.

For the support conference, the starting point could be the operational mess around product launches. Tickets arrive before internal documentation is ready. Customer questions change as teams discover problems. Managers have to decide which issues need escalation and which need a clearer answer. A session about those decisions has a concrete purpose that a support leader can recognise immediately.

Ask the speaker what they actually intend to cover. What question will attendees be able to answer more confidently? What experience level is the session for? Will they discuss an example, run an exercise or explain a method? Use their answers to prepare the description. Don't promise templates, personal feedback or access to confidential examples unless those are genuinely part of the session.

A hypothetical announcement could read: "Product launches can leave support teams answering questions before the internal answers are ready. At Support Operations Day, I'll explain how to organise escalation decisions and keep customer responses consistent during launch week. The session is for people managing small support teams. The conference details and tickets are on the event page."

That wording still needs the actual speaker's approval. They may prefer a different example or feel your description overstates the session. Make editing easy and invite corrections. You're preparing useful starting material, not asking them to perform enthusiasm or publish your opinion in their name. Their own explanation may sound less polished and tell prospective attendees much more.

You also need a reason to buy the conference beyond that single session. Explain how the wider programme serves the same audience, what the ticket includes and which other parts might be relevant. Avoid suggesting someone can attend a full conference for one conversation that isn't guaranteed. A strong session introduction should lead to an accurate view of the complete purchase.

Keep the promotional request small and specific

Ask for one contribution at a time. Sending an entire campaign calendar can make a simple request feel like another job. Start with the action you've agreed, include the proposed publication window and explain what happens next. If the speaker agrees to more later, prepare the next contribution when there's a useful reason to communicate again.

The best format depends on their habits. Someone who writes regularly may prefer a short text post. A newsletter writer may want a paragraph they can adapt. A speaker comfortable explaining their work on camera may offer a brief session introduction. You don't need every speaker to produce the same format, and you shouldn't require a new channel just because your campaign uses it.

Avoid asking for follower lists, access to accounts or introductions to everyone in their network. You can ask whether a professional association or community would welcome the session, but the speaker should decide whether and how to approach it. Respect the community's rules. An invitation that ignores those rules can damage both the speaker's relationship and your conference's reputation.

Treat a newsletter mention as communication to the speaker's audience, rather than a reason to acquire that audience's contact details. For UK activity, the ICO's direct marketing guidance explains the need to plan lawful data use and respect marketing preferences. Requirements differ by market and recipient, so review the rules that apply to your actual campaign.

Offer help with the preparation and retain one named contact for questions. If the speaker replies with an edit, that person should resolve it without sending them through separate marketing, programme and sales teams. You can coordinate internally. From the speaker's perspective, the request should remain easy to understand and possible to complete alongside their existing work.

Be realistic about what counts as completed. A speaker who agreed to share an announcement has completed it when they publish the agreed announcement. They haven't failed because the post generated fewer ticket sales than you hoped. Use the results to improve the offer and future planning, while honouring the difference between an agreed action and a hoped-for commercial outcome.

For a panel, agree who is speaking about the session publicly before sending individual requests. You might ask each panellist to explain the part they will contribute, provided the moderator approves the overall description. That prevents several announcements promising different versions of the same discussion. It also avoids making the most active panellist responsible for promoting everyone else. If a speaker would rather share the organiser's confirmed announcement, make that option available. A simple, accurate introduction is more useful than a lengthy contribution that nobody has time to check.

Prepare the facts before you send copy

Send one current set of details with the request. Include the confirmed session title, the speaker's approved name and role, the conference date and location, what the ticket covers, the purchase link and any genuine deadline being mentioned. If the schedule is provisional, say so. A speaker shouldn't have to compare previous emails to work out which information is accurate.

Check their name and employer details with them. A job title copied from an old biography can be wrong. Their company may permit a factual affiliation but prohibit using its logo or implying sponsorship. Ask who needs to approve those details, and keep the approved wording with the session record. Approval to appear on an agenda doesn't settle every other use.

Separate the information the speaker must preserve from the wording they can change. The date, venue and ticket conditions must remain accurate. The explanation of why the topic matters can usually be in their own words, provided it doesn't introduce unsupported promises. That flexibility makes participation easier without allowing important purchase information to drift as the material is adapted.

Don't create false urgency on their behalf. If you mention an early price deadline, confirm that the ticket release really ends then. If availability changes, update the speaker before the next post. A scheduled message saying tickets remain available is a problem when they've sold out. The operator needs to keep speakers informed because the operator controls inventory and release changes.

If a discount seems necessary, first ask what obstacle it solves. A relevant attendee may need budget approval or a clearer programme description rather than a lower price. Discounts reduce revenue on tickets that might otherwise sell at full price. Our event ticket pricing guide helps you consider the offer alongside the event's costs and commercial requirements.

Choose one working purchase link and test it before sending. Open it on your phone, check the session information, select the relevant ticket and inspect the displayed price and conditions. If the link redirects, make sure the destination is still correct. You don't want a helpful speaker introducing qualified buyers to a page that leaves basic questions unanswered.

Send the message when buyers can act on it

Time the first announcement around confirmed information and open ticket sales. If your tickets aren't available yet, decide whether you're asking people to join a properly explained waiting list. Don't let the speaker imply that attendees can secure a ticket when they can only express interest. The next step should match what your conference is ready to offer.

Think about the buying process for your audience. A professional attending a paid conference might need manager approval, a purchase order or permission to travel. Their decision may require more time than buying a local evening event ticket. Ask past attendees how they arranged attendance, and use your own sales history where you have it instead of copying someone else's campaign dates.

After the announcement, a session preview gives the speaker a different reason to communicate. It could explain a decision they'll explore or an assumption they'll challenge, with a clear connection to the full programme. This is more useful than sending the same announcement again. Let the substance of the session determine whether another message would add anything for prospective attendees.

A later reminder can answer a practical question: whether the session is included in the standard ticket, whether a workshop needs separate booking or when a confirmed ticket release ends. Send that information only when it's correct and useful. If nothing has changed, don't ask the speaker to invent a new reason for repeating your purchase link.

Plan publication windows with the speaker rather than insisting on an exact minute unless there's a real coordination need. They may know when their audience reads their newsletter or engages with their posts. Your campaign can accommodate that knowledge. Keep a note of the agreed window so you're following up on an actual arrangement, rather than treating every quiet day as a missed obligation.

When someone hasn't replied, send one clear reminder through the agreed contact channel. Say what you're waiting for and whether a later window still works. If they cannot participate, adjust your plan and continue promoting through channels you control. An unanswered email should prompt a practical decision about the campaign, not a sequence of increasingly uncomfortable requests.

Have a correction process ready before publication. If a speaker withdraws, a session moves or the format changes, contact the people who have shared the affected details. Tell them exactly what changed and which information needs updating. Your event page should explain the current programme and relevant ticket conditions. Don't ask speakers to keep promoting an appearance that is uncertain. If an existing post cannot be edited, agree an appropriate correction and make the updated information easy for buyers to find. Check scheduled communications too, because an accurate correction today won't prevent an old announcement appearing tomorrow.

Explain paid relationships and permissions clearly

A speaker sharing their appearance is not automatically doing the same job as a paid influencer. Still, the relationship and the content matter. Payment, free services, commissions or other benefits can affect disclosure requirements when the speaker endorses the conference. Don't decide that "speaker" is an exemption or assume a visible name on the agenda explains every financial arrangement.

For promotions affecting US consumers, the FTC's disclosure guidance says material relationships should be clear in endorsements, and those relationships can include money or other benefits. It also explains why a disclosure buried after a reader expands a post may be missed. Review the actual arrangement and place required disclosures where people will encounter the promotional message.

For UK campaigns, consult the ASA's guide to identifying advertising, which includes affiliate marketing and disclosure advice. The ASA notes that some legal references are being updated. Check current requirements for your circumstances instead of treating a generic label as universal advice. If you're paying for controlled promotional content, agree the disclosure treatment before the speaker prepares it.

Keep disclosure language separate from the speaker's factual session explanation in your approval process, so neither is accidentally removed during an edit. If a format changes, review it again. A disclosure suitable for a written post may need different placement in a video. Your team and the speaker should understand who's checking the final version and how corrections will be handled.

Also agree how you may reuse the contribution. Permission for a speaker to publish on their own account doesn't automatically authorise paid ads, website endorsements or edited clips. Ask about the specific use, duration and context. Keep their approval. If your later advertisement changes the meaning of what they said, return to them for approval rather than relying on the original permission.

Employer review can affect timing as much as the speaker's own availability. Someone discussing their company's work may need to remove customer information or obtain approval for a public example. Leave room for that process. If approval isn't possible, use a broader session description or skip that contribution. You can still market the confirmed conference without pressing someone to disclose information they cannot share.

Be careful when a speaker's commercial interests overlap with your audience. A consultant may be happy to promote a conference because prospective clients will attend. That doesn't mean attendees agreed to receive their sales emails or that your conference endorses their services. Explain the boundaries of any attendee interaction and keep sponsored content accurately described. If a speaker is also a sponsor, make sure both relationships are understood before you prepare promotional copy. The buyer should be able to judge the session on an honest description of who is presenting it and what they will actually cover.

You can also offer an alternative when approval is slow: "Would you prefer to share our published session description once your team has approved it? We can hold your announcement until that is ready. Please flag any wording about your employer or examples that we should remove." That keeps the decision clear without asking the speaker to negotiate internal restrictions on your deadline. Confirm the revised publication window, and update your own campaign plan so colleagues know what to expect next.

Help interested people decide whether to buy

The purchase page should continue the explanation the speaker started. Someone clicking because they manage support launches should find the relevant session, understand who the conference serves and see how the programme connects to their work. If they land on a generic page full of speaker names, you've asked them to reconstruct the reason for attending themselves.

Use the session's confirmed description on the event page and make the full agenda easy to find. Explain whether sessions overlap, whether any require advance booking and what happens if an attendee cannot attend every session. The relevant question is what the buyer can actually do with their ticket. Don't make the advertised session appear accessible if its room or format has separate restrictions.

State what the price includes. Lunch, workshops, recordings, networking sessions and taxes or fees should follow your actual offer and the applicable requirements. A speaker might mention one part of the programme while the buyer wants to know the complete cost of attending. Our event landing page guide covers the page information that supports that decision.

For an employer-funded purchase, provide accurate information people can use in an approval request. That may include the agenda, attendance dates, ticket terms and invoice arrangements you actually support. A short explanation of the relevant learning goals can help, but don't promise a financial return the conference cannot establish. The buyer and their employer still need to judge its value.

Your checkout deserves the same attention as your speaker messages. Loopyah's ticket selling platform lets buyers check out as guests, automatically opens the next ticket release when one sells out and reports sales by source. That helps you handle purchases and review recorded results while you focus on explaining why this conference is worth attending.

Keep the path useful for someone who isn't ready to buy immediately. Let them read the agenda and conditions without surrendering contact details. If they choose to receive updates, explain what they'll receive and respect that choice. When your team follows up with interested people, answer their actual questions about attendance rather than sending another generic announcement of the same speaker.

Measure participation and sales without claiming too much

Set up tracking before the first contribution goes live. Use a consistent way to identify the speaker and the contribution, whether your ticketing system provides referral links or you use campaign parameters. Keep a record of what was published and when. Otherwise, you may see a change in traffic without knowing which message or publication window you're comparing.

Google's campaign URL guidance explains how campaign parameters identify referred traffic in Analytics. Keep platform and channel names consistent, and distinguish a speaker's contribution with an agreed content label. These labels identify visits recorded through the link. They don't capture every person who saw a post, remembered your conference and returned through another route.

Check what your setup actually records across the purchase process. If checkout runs on a different domain, or a link passes through a redirect, confirm that your reporting still works as intended. Test it through a supported process. Don't report that a link tracks completed ticket sales merely because you can see page visits. Visits and paid orders answer different questions.

For each contribution, look at whether it reached a relevant audience, brought interested visitors and was associated with completed purchases where tracking supports that view. Compare ticket types and refunds when reviewing revenue. A contribution producing many curious visitors may need clearer audience language. A contribution producing fewer visitors but useful purchases may deserve more attention next time.

Keep the interpretation modest. Google describes attribution as assigning credit to interactions along a route to an important action. Recorded credit does not prove those purchases would disappear without the speaker's post. Other advertising, colleague recommendations and earlier attendance may have helped the buyer decide. Describe tracked results as tracked results, with the method and its limits.

Don't sum every channel's reported sales and assume the total is additional sales generated by your campaign. Different tools can credit the same order. Reconcile reporting against actual paid orders and use a consistent approach when comparing contributions. If your tracking is incomplete, say so. You can still learn from buyer questions, relevant comments and the speaker's feedback without manufacturing precise revenue claims.

Use the results to make the next request better

After the conference, thank speakers for the contribution they agreed to make and explain what you learned. Useful feedback might be that their session preview brought questions about workshop access, or that buyers needed a clearer description of the intended experience level. Share aggregated information you can substantiate. There's no need to disclose attendee details to make that conversation helpful.

Ask what felt easy and what took more work than expected. You may learn that the draft arrived too late for a newsletter, that employer approval required a longer lead time or that the announcement described the session poorly. These are specific changes your team can make. Record them with the speaker's preferences so next year's invitation doesn't repeat the same avoidable problem.

Review your own workload too. A contribution requiring repeated revisions and extensive coordination may be expensive even without a promotional fee. Compare that effort with the useful outcomes you can observe, while considering the speaker's broader contribution to the programme. You aren't assessing their worth as a speaker solely through link performance; you're deciding how much promotional preparation is sensible.

Keep the parts that helped buyers understand the conference. If practical previews worked, prepare those earlier next time. If a discount mostly reduced the price for existing buyers, reconsider it. If several speakers declined promotion, budget for channels you control. Your planning should reflect what people agreed to do and what the evidence supports, rather than another optimistic assumption about access to their audiences.

Start with the next speaker you're confirming. Explain whom the conference serves, ask which contribution they'd be comfortable making and write down what you agree. Then prepare the confirmed session details and test the purchase page before asking them to share it. That sequence gives you a realistic piece of the campaign to coordinate while keeping responsibility for a commercially sound conference with your team.