Build the audience once, send approved WhatsApp templates and rich email at the channel's pace, and let every reply land in the inbox where Kaylee and your team answer it. Then retarget exactly who read but did not reply.
100,000 recipients per campaign ✦ Replies in the inbox ✦ Lead signals back to Meta
The most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
A segment is a saved, named audience of up to 200,000 people, identified by phone number or email, with optional per-person values you can use in messages. Fill it five ways: paste, upload a CSV, add every contact matching a filter, add every chat on a channel, or take the recipients of a past campaign, all of them or only the ones who read, replied or clicked. The same number written three ways is one person.
Audiences from contacts, chats, CSVs, segments or a past campaign's stage, with per-person attributes for the message.
Learn moreApproved templates on WhatsApp Official at scale, free text on unofficial, rich HTML email, and push through your own app.
Learn moreReplies land in the inbox on the customer's record, where bot journeys and Kaylee answer and your team sees the escalations.
Learn moreEvery recipient keeps a stage. The next campaign goes to who read but did not reply, or who clicked.
Learn moreProactive WhatsApp needs an approved template. The builder mirrors Meta's components, header, body, footer and buttons, with live validation and a preview on iOS and Android in light and dark. Build carousels of two to ten cards, limited-time offers with a live countdown and a copy-code button, and authentication templates in several languages in one submit. Named or positional placeholders fill from contact fields, global values or CSV columns, with a fallback when a value is missing.

A reply to a campaign is an ordinary inbound message, so the channel's bot journey fields the predictable ones, Kaylee answers the rest and your team sees the escalations in the same queue. For click-to-WhatsApp ads, the workflow stages and dispositions you choose are reported back to Meta's Conversions API, keyed to the ad click, so Meta optimises for leads that turned out to be good. At the top of the funnel, Content Studio publishes the posts that bring readers to the chat widget in the first place.
Chats, contact filters, CSV, saved segments and past-campaign stages, saved as a segment for next time.
A future send time, the channel's rate cap, 1 to 10 retries, and cancel mid-run.
Template slots rendered for a real recipient, with the fallback for a missing value.
Sent, queued, retrying and failed with reasons, refreshed every few seconds.
Scrape your pages or a competitor's, draft in your brand voice, refine with diffs.
A hero image in seconds and a sixty-second avatar video in the background.
Open Graph, structured data, sitemap, RSS and the AI-crawler summary, live in seconds.
Readers who ask a question become CRM contacts your campaigns can reach.
Meta Instant Forms become leads with campaign, ad set, ad and form attribution.
Report which click-to-WhatsApp leads were good, keyed to the click, so campaigns optimise for them.
Read-no-reply, clicked, failed: any stage of a past campaign is the next audience.
Chats, dispositions and survey responses with the module's filters, for your own dashboards.
In practice
A villa operator saves last summer's Goa guests as a segment with each person's offer code as an attribute. A winter template with a carousel of villas goes out at 10 on Friday at the channel's pace. Replies land in the inbox, where the bot journey answers availability and Kaylee holds villas through the booking tool. On Monday, everyone who read but did not reply gets a one-line nudge, and the bookings that came from click-to-WhatsApp ads are reported back to Meta as purchases.
Approved templates on WhatsApp Official, opt-outs honoured as permanent failures, quiet hours and a daily cap on promotional push, and audiences and messages scoped to your organisation in the region you choose.
Visit the trust centerSave one segment, approve one template and schedule the first send today.
The things marketing teams ask before they move their campaigns.
Campaigns on WhatsApp, email and push to audiences built from chats, contact filters, a CSV, a saved segment or a stage of a past campaign; approved WhatsApp templates with carousel and limited-time-offer shapes; per-recipient personalisation; pacing and retries; and every reply landing in the inbox where bot journeys, Kaylee and your team answer it. Content Studio writes the blog posts that bring traffic in.
Up to 100,000 recipients per campaign from a segment of up to 200,000 members, each person counted once. WhatsApp Official templates send at around 600 messages per minute; unofficial WhatsApp and email at around six per minute by default, tunable. Recipients are matched and prepared in the background, so a large campaign saves straight away.
Replies come back into the same inbox as everything else, on the customer's record, where a bot journey fields the predictable ones, Kaylee answers the rest and your team sees the escalations. And the next campaign can target exactly who read but did not reply, or who clicked, because every recipient's stage is kept.
Yes. Template campaigns fill each slot from a contact field, a global value or a CSV column, with a fallback for recipients who have no value. Free-text and email campaigns use named tokens such as first name or booking id. Segment attributes, an offer code or a villa name, work as columns too.
Proactive outbound on WhatsApp Official needs an approved template. The builder mirrors Meta's components with live validation, previews on iOS and Android, submits for review, which takes 24 to 48 hours typically, syncs status and quality ratings by webhook, and imports templates you already have with another provider.
Per recipient: queued, sent, delivered, read, replied, clicked, retrying or failed with the reason. On the campaign: counts and progress refreshed every few seconds while it runs. Afterwards: any stage becomes the audience of the next campaign, and conversation outcomes can be reported back to Meta as lead signals for click-to-WhatsApp ads.
Yes. A reply to a campaign is a normal inbound message on the channel, so the channel's bot journey and Kaylee handle it like any other, including asking your team before anything that needs approval.
The top of the funnel: blog posts researched from your sources, written in your brand voice, published to your site with the chat widget on them, so a reader with a question becomes a contact you can later include in a segment. See Content Studio.