Skip to article
BITTUMailPOWERED BY BITTU ICLOUD
The Mail BlogEmail templates

Request a Copy of a Professional Event’s Published Slide Deck

A polite, ready-to-adapt email for requesting an event slide deck, with prompts to identify the session, check sharing restrictions, and confirm the intended recipient.

Paper folders, message cards and a clock arranged on a sage background.
Original BITTU Mail editorial artwork. Illustrative image.

A useful slide-deck request makes it easy for an organizer or presenter to recognize the session and answer without guessing what you need. It also acknowledges that slides may not be shareable, or may be available only through an event page or another approved route. Use the template below after checking any event follow-up materials you already received. Replace the bracketed fields, choose the right recipient, and keep your request focused. If the deck cannot be shared, a brief question about an approved alternative is often enough.

The useful bits

  • Name the event, session, presenter, and date so the recipient can identify the right deck.
  • Ask whether sharing is permitted instead of assuming the slides are available.
  • Check the recipient and follow-up materials before sending, then acknowledge the response.

Check before you write

Look through the event program, attendee email, or event page for a published deck or instructions about materials. If the slides are already available through an official channel, use that route rather than asking someone to send a separate copy.

If you do not see them, identify the session as precisely as you can. Include the event name, session title, presenter’s name, and event date. If you attended one of several sessions with similar topics, this detail helps distinguish the right presentation.

Choose who should receive the request

Use the organizer’s published contact for attendee questions when one is provided. If the presenter has invited follow-up directly, you can write to them instead. When you are unsure, send one message to the most relevant contact and ask them to redirect it if needed; avoid sending the same request to several people at once.

Before sending, check the address and the To field. If you are writing on behalf of a group, say who you mean by “we” and ask whether the slides may be shared with that group. Do not assume permission to forward a deck just because you were sent a copy.

A considerate request you can adapt

Keep the note brief, include enough context to identify the session, and make the sharing question explicit. The bracketed fields are prompts, not text to leave unchanged. Adjust the request if you want a personal copy, a team copy, or a link to an official posting.

EXAMPLE / ADAPT TO YOUR SITUATION
To: [organizer or presenter email]
Subject: Slides from [event name] — [session title]

Hello [name or event team],

I attended [event name] on [date] and found [session title], presented by [presenter name], useful. Would you be able to share a copy of the published slide deck, or point me to where it is available?

Before sharing, could you please confirm whether the slides may be distributed to [intended recipient: me only / our team at team@example.com]? I understand if any content is restricted or the deck is not available for distribution.

Thank you,
[your name]

Make the sharing request precise

The phrase “published slide deck” can mean a public copy, an attendee resource, or a version cleared for a particular audience. State who should receive it rather than leaving that question open. For example, say “for my own reference” if you want a personal copy, or identify the team or colleagues if you hope to circulate it.

Ask about restrictions without pressing for details the recipient may not be able to provide. A deck might not be shareable, or the sender may be able to direct you to an approved version instead. If the answer is no, you can ask whether a public summary, recording, or other material is available—but do not treat those alternatives as guaranteed.

Review the message before sending

A quick check can prevent an avoidable back-and-forth. Confirm that the session title and date are accurate, the greeting fits the recipient, and the intended audience is clear. If you mention a team address, make sure it is the correct one and that sharing with that group is genuinely what you want.

Keep the tone appreciative, but avoid implying that the recipient promised to provide the slides. A specific request with room to decline is clearer and more courteous than a demand or a long explanation.

  • Can the recipient identify the event and exact session?
  • Have I checked whether the deck is already posted or covered by event instructions?
  • Did I name who should receive the slides and ask whether sharing is allowed?
  • Is the destination address correct, and have I removed every bracketed prompt?

Confirm what happens next

After sending, check your sent message to confirm the request went to the intended address and includes the session details. If you receive a link or attachment, verify that it is the material the recipient meant to share and follow any stated limits on access or forwarding.

If there is no reply, allow a reasonable interval and consider one short follow-up in the same thread, especially if the event has a stated contact process. Repeat the session title and ask whether the request reached the right person. If the deck cannot be shared, thank the recipient and use any alternative they have approved.

About this guide

Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.

View current plans · Security information · Suggest a correction