# Review and activate guest automations

**Console: Marketing → Campaigns**, then **Automations** in its workspace. For
the manager responsible for automated guest contact. A draft never sends;
activation can begin future sends and requires the relevant send permission.

## Start with drafts

**Install standard automations** currently adds ten prepared automations as
drafts and skips already-installed entries. The confirmation warns that the
post-visit note and review ask cover the same moment; review which to activate
so guests do not receive overlapping messages.

Alternatively select **New automation**. Name it, choose its trigger segment,
configure timing and cooldown, and prepare its first email. Add follow-up steps
under **Journey** where needed; review the wait after each previous step and
save the draft. This is a linear journey, not a branching workflow.

## Check before activation

Review trigger eligibility, missing profile data, audience overlap, content,
restaurant identity, consent, send windows, and cooldown. Multiple active
automations using the same segment can each send to the same guest. Check
waiting recipients and earliest due time; a count is not proof they will all
receive a message immediately.

The message classification is set by TablePort for the template. Marketing
requires this business's marketing permission. Service-message templates
restrict content to their stated administrative or customer-service purpose;
they are not a route for advertising to non-consenting guests. Do not reward
reviews or choose feedback recipients based on how happy they seemed.

Activate using the confirmed action from the list only after review. For a guest
promise, verify terms, availability, staff fulfilment, and the required
restaurant acknowledgement. Verify the active state and resulting queue.

## Live edits, pausing, and recovery

Saving an active automation's content keeps it active and can affect future
sends. Pause it from the list before edits that should remain a draft workflow.
A team member with send permission must activate or save consequential live
changes. Reopen and verify state after every uncertain save.

A paused or draft automation is not currently sending. Deleting a journey step
removes its subject/content; review the confirmation. If stored email content
failed to load and the editor shows a placeholder, reload before saving.

Use its performance view for delivered, indicative opens, clicks, and outcomes.
If a send is uncertain, inspect existing state and contact support instead of
repeatedly activating or creating a replacement automation.