The following email template can be used to share final reminders and onsite instructions for exhibitors using the Developer Kit. It is intended as a starting point and should be customized to fit the details, tone, and requirements of your event.
NOTE
The suggested send date for this email is three (3) weeks before the event start date.
Subject:
Developer Kit Know Before You Go for {{EventName}}
Email Body:
Hi {{BoothAdminFirstName}},
Thank you for supporting {{EventName}} in [add location] on {{EventStartDateShort}} - {{EventEndDateShort}}. We are excited to partner with Cadmium event technology to offer the Eventscribe Developer Kit API for this event.
If you haven't already, please immediately ensure your third-party developer has configured and tested the connection to the API.
Please share the following onsite details with booth staff:
- An internet connection is required for the Developer Kit API to function.
- Exhibitor WiFi:
- [insert network name]
- [insert password]
- Attendee profile and demographic data is pulled from registration. If data is missing, the registrant most likely didn’t provide it on their registration form.
- It may take a few minutes for a new registrant or profile changes to be reflected in the API. If you receive an error, wait a few minutes and try again.
- Reference the Developer Kit API Overview for FAQs and troubleshooting support.
- For onsite support, [insert onsite support desk location and contact information].
In case you need to access the Lead Capture Portal, here is your unique login URL for {{CompanyName}} – Booth {{BoothNumber}}: {{ExhibitorLoginURL}}
*If your organization has more than one booth, each will have a unique URL.
If you have any questions, don't hesitate to reach out at {{SupportContactEmail}} or {{SupportContactPhone}}.
Regards,
[add signature]
Terms & Conditions
By using Eventscribe Lead Capture, you agree to Cadmium’s Privacy Policy and Terms & Conditions.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article