Salon
Hi {owner}, I help salons organize missed appointment inquiries, after-hours messages, and follow-up reminders. Could I send a short audit idea for {business}?
Template library
Reusable scripts and client communication templates.
These templates are starting points. Outreach drafts must be reviewed, personalized, and sent manually.
Outreach templates
Permission-based first messages by niche.
Barber
Hi {owner}, quick idea for {business}: a simple workflow that catches website, Instagram, and phone-note inquiries in one tracker. Want a 60-second demo?
Restaurant
Hi {owner}, I noticed restaurants often miss catering, reservation, and event inquiries when messages are scattered. I can send a simple workflow example if useful.
Property manager
Hi {owner}, I help property teams organize maintenance requests and owner summaries without automating sensitive tenant decisions. Want a quick workflow audit?
Security company
Hi {owner}, I build approval-based workflows for guard notes, daily summaries, and admin follow-up. I can send a demo using fake report data.
Gym
Hi {owner}, I help gyms track membership inquiries, trial follow-ups, and review requests with a simple human-approved workflow.
Cleaning company
Hi {owner}, I had an idea to capture quote requests, assign follow-ups, and summarize open leads each week. Want me to send a quick example?
Repair service
Hi {owner}, I help repair businesses keep quote requests, missed calls, and status follow-ups organized. Could I send a short demo workflow?
Local retail
Hi {owner}, I help local shops track product questions, special orders, and review requests in a simple owner-visible workflow.
Sales call scripts
Short scripts for discovery and common objections.
Discovery call
What happens today when a customer reaches out after hours? Where does that inquiry get saved, who owns follow-up, and what breaks most often?
Pricing explanation
The setup fee covers building and testing the first workflow. The monthly fee covers monitoring, adjustments, and support so it stays useful.
Too expensive objection
That makes sense. The safest starting point is one small workflow with a clear scope. If that is not worth solving now, we should not force it.
Need to think objection
No problem. I will summarize the workflow, price, exclusions, and next step so you can review it without pressure.
Already have a website objection
Good. This does not need to replace your website. We can usually connect to the existing form or add a small intake path.
Can AI really do this objection
The important part is the workflow, not AI magic. AI can help draft and summarize, but owner-approved rules control the system.
What if it breaks objection
Every workflow needs a fallback. We test it, document failure modes, and keep owner notifications visible.
I do not trust automation objection
That is reasonable. The starter system keeps customer-facing actions approved and focuses on tracking, reminders, and visibility.
Proposal templates
Package-specific proposal starters.
Starter
Starter System proposal: inquiry form, approved auto-reply, lead tracker, owner notification, follow-up reminders, weekly summary, and handoff.
Growth
Growth System proposal: Starter deliverables plus review request workflow, quote follow-up workflow, simple dashboard, and monthly optimization.
Ops Pro
Ops Pro proposal: Growth deliverables plus SOP assistant, staff/admin workflow, recurring reports, custom dashboard, and priority support.
Custom workflow
Custom workflow proposal: define one workflow, approved tools, data limits, testing checklist, human approval points, monthly support, and exclusions.
Client emails
Emails to manage delivery without overpromising.
Welcome email
Welcome to the project. I will keep the first workflow scoped, tested, and approval-based. Please review the requested access and copy items.
Information request
To start safely, please send your approved business hours, service areas, contact rules, follow-up timing, and the tool accounts you own.
Project started
The build has started. I will test with fake inquiries first and share the workflow before anything customer-facing is activated.
Test request
Please review this test workflow and confirm the wording, notification recipient, reminder timing, and fallback process.
Handoff
Here is the handoff summary: workflow map, tool links, test results, approved copy, fallback steps, and support process.
Monthly report
This month we reviewed lead counts, open follow-ups, workflow failures, and recommended improvements. No sales outcome claims are included.
Renewal
Your monthly support renews on {date}. Current scope includes monitoring, minor improvements, and monthly review.
Cancellation response
Thanks for the update. I will document the cancellation date, export any available data, and confirm which client-owned tools remain active.
Delivery SOPs
Repeatable delivery checklists.
Onboarding
Confirm scope, tools, approved copy, data limits, owner contact, testing window, and fallback process.
Automation testing
Submit fake inquiries, verify tracker rows, confirm notifications, test reminders, review weekly summary, and document failures.
Handoff
Record Loom, share workflow map, list owners, document how to pause automation, and confirm support boundaries.
Support
Log issue, classify impact, pause risky workflow if needed, test fix, notify owner, document root cause.
Monthly review
Review counts, failures, stale follow-ups, client feedback, copy changes, and upsell opportunities.
Refund/scope control
Compare issue to written scope, identify deliverable gap, propose fix or refund path, and avoid adding unapproved work.
Legal/scope disclaimers
Plain-language scope controls. Not legal advice.
No revenue guarantee
This workflow is designed to reduce missed inquiries and improve follow-up consistency. It does not guarantee revenue, bookings, or sales.
Human approval required
Customer-facing messages, outreach, proposals, sensitive data workflows, and tool changes require client approval before activation.
Client owns tools/accounts
The client owns their accounts, data, and access. TrueGuide does not take ownership of client tools.
Sensitive data excluded
Medical, patient, payment, legal, financial, and other sensitive data workflows are excluded unless a separate compliance review is completed.
Spam compliance reminder
Outreach drafts are for manual review and manual sending only. Do not bulk-send or scrape contacts without compliant consent and review.
Cancellation terms placeholder
Cancellation terms should be confirmed in the written agreement, including renewal dates, data export, and support end date.