The campaign flow includes behavior-based audience segments
Settro's campaign creation flow includes all customers, repeat customers, inactive customers, high value, and new customers as explicit audience options.
Restaurant re-engagement campaigns work best when owners can target the right audience, send through the right channel, and see delivery plus downstream results without guessing. Settro's public campaign hub is built to frame that workflow clearly: targeted outreach, channel selection, delivery reporting, and dashboard-level visibility into what happened next.
This hub now surfaces public proof from the app workflow before the detailed campaign question pages rely on those claims. The proof includes dashboard screenshots from Settro's app docs and exact capability language already present in the product surface.
Settro's campaign creation flow includes all customers, repeat customers, inactive customers, high value, and new customers as explicit audience options.
The public proof on this page is based on Settro's app workflow, which supports Instagram DM, Facebook DM, and SMS channel targeting with plan-aware entitlements.
Settro's campaign detail workflow exposes delivery metrics and completion status so owners can separate campaign activity from campaign outcome.
Settro's dashboard loads missed-call recovery, order sources, busy-hour signals, and other summary views that help owners tie campaign work back to operating results.
Campaigns perform better when the restaurant defines who the message is for before writing the message itself.
Instagram, Facebook, and SMS should be selected intentionally based on entitlement, customer behavior, and the kind of campaign being run.
The restaurant needs to see what was sent, what was delivered, and what happened after the campaign so the next campaign improves.
Re-engagement campaigns are strongest when they are not isolated from the rest of the restaurant's demand system. The same business also needs phone recovery, social ordering, and clear reporting so campaign activity can be interpreted in context.
A guest may first enter the system from a missed phone call, a DM conversation, or an earlier order.
Campaigns can bring that guest back through Instagram, Facebook, or SMS when the targeting is clear.
Dashboard reporting matters because it helps the owner compare campaign activity with broader order-source and performance signals.
Because the campaign question pages should cite claims that are already surfaced publicly on settro.net instead of relying on private product truth alone.
No. The point is to show the workflow and the reporting surface clearly enough that owners can evaluate whether the system matches how they want to run campaigns.
Start here if you are evaluating the campaign workflow itself. Start with the question pages if you want an answer about inactive customers, KPIs, attribution, or specific campaign types first.
These routes answer explicit owner questions in plain operator language first. Use them when the search intent is a problem statement, then come back here when you want to evaluate the workflow itself.