Email from your own domain, threaded with everything else
Verify a sending domain with DKIM and SPF, point a forwarding address at Lodgestory, and email becomes a channel: the same send request, the same webhook envelope, the same guest record as WhatsApp and the phone.
Your domain, DKIM and SPF ✦ Inbound forwarding address ✦ Same API as every channel
The most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
BBingo Hotels
Verified once, trusted by inboxes
Add Email from Connections and type your sending domain. Lodgestory generates the DKIM and SPF records; add them to DNS and a status check flips the card to Verified, usually within an hour of propagation. Mail then goes out from your operator's own domain, and an inbound forwarding address lands replies in the same inbox.
- Not a white-label subdomain you have to explain to guests.
- One record per guest: an email thread and a WhatsApp chat from the same person sit on one timeline.
- Attachments and internal notes work as on any channel.
Why teams build on it
Send with the universal request
The email channel id in the same send-message call. Templates stay a WhatsApp concept; email sends free text and media.
Receive in one inbox
Replies arrive on the forwarding address and thread into the guest's conversation, with the chat state and assignee carried along.
Hear about it by webhook
message.received and message.sent with the full message, plus the chat and ticket events every channel shares.
Email events on the shared envelope
Every inbound email is a message.received delivery with the text, sender and thread id; every send is message.sent. Tickets raised from an email thread, assignments and resolution fire the same events as any conversation, so one handler covers every channel.
- channel_type: email on every message payload.
- Signed, retried, logged like every delivery.
- Replay any delivery for thirty days.
Ready to build on Email?
Create an organisation, enable Developer Access and run your first request against your own workspace today.
Questions, answered
What engineering teams ask before they integrate.
No. Add your domain in Connections, publish the DKIM and SPF records Lodgestory generates, and send from your own address through the same messaging API and the inbox.
Lodgestory gives you a forwarding address. Forward your support or reservations mailbox to it and every email lands as a conversation on the email channel, threaded with the guest's other channels.
No. Create a chat with the guest's email on the email channel, then POST /messaging/send-message with type "text" or media. Webhooks deliver replies as message.received.
Yes. Assign a bot journey to the email channel and the same escalation to Kaylee, ticketing and team routing applies as on chat channels.