AUTOMATION PLAYBOOK

Google review request

24 hours after a completed visit or booking, the client gets one SMS with a Google Business link — no awkward ask at checkout.

More 5★ reviews without asking at the counter.

Trigger

24h after completed visit / booking

Automated flow

  1. 1 SMS with Google Business link
  2. 2 CRM tag “review_sent”
  3. 3 Skip if already reviewed
Enable this playbook

Example scenario

Guest had dinner Saturday. Sunday evening SMS with review link. CRM tag “review_sent”; on the next visit the playbook does not resend.

After the call: Google review request

More 5★ reviews lift Google Maps visibility. Automation handles throttle and platform policy alignment.

When it runs

The playbook starts automatically when Coldbot tags a call or event as: “24h after completed visit / booking”. You can narrow filters (location, channel, business hours) without changing the voice script.

What happens automatically

Each step runs in sequence (or in parallel where noted). No copy-paste between voice AI, SMS gateway, and CRM.

What you configure

Tunable during onboarding — copy, thresholds, and channel priority:

Recommended integrations

Native connectors or Zapier/Make/webhooks. Status “coming soon” means we enable it on request during rollout.

Works with voice templates

Deploy these agent scripts together with the playbook — same disposition tags power both sides:

Onboarding checklist

We configure this playbook during Coldbot setup — usually in one working session:

Zapier / Make recipe

We export a starter automation: Coldbot webhook → your stack. Field mapping is done in onboarding.

FAQ

Frequently asked questions

Do I need a developer?

Not for standard stacks (SMSAPI, Google Calendar, HubSpot, Slack). Custom webhooks usually need about one hour of IT time.

Can we change copy and timing?

Yes — triggers, filters, SMS templates, and quiet hours are fully configurable in the dashboard or with our team.

Is this included in setup?

One playbook is configured during onboarding; additional playbooks are added per package or integration bundle.

How do we test before go-live?

Sandbox numbers, test calls, and a dry-run checklist — we do not enable production SMS until you approve samples.

Does this violate Google rules?

We send the public review URL, no incentives for ratings — per guidelines.