Use cases / All trades / Set up what you already pay for
Set up what you already pay for: on-my-way texts, invoice reminders, and native follow-ups
The owner pays for a job-management app but has its automations switched off.
The business case
This one is mainly a time-saved case, so we don't claim revenue. Assumptions (illustrative): 40 jobs/invoices per week touched by native automations, about 2 min saved each, staff time valued at $30/h, running cost $0/mo, setup $600.
| Case | Hours saved / mo | Value of time − running cost |
|---|---|---|
| Conservative | 2.9 h | $87 |
| Expected | 5.8 h | $173 |
| Optimistic | 8.7 h | $260 |
Time saved only matters if it gets used on billable work. Track the before and after.
Requirements & gating
- Jobber: public GraphQL API using OAuth. A custom integration can connect to up to 5 Jobber accounts without App Review; beyond that it must pass Marketplace review. verified
- Housecall Pro: the public API and webhooks are MAX plan only, and the owner generates the API key. Webhook events include
estimate.sent,job.completed,lead.created,invoice.paid. verified - ServiceTitan: API access is partner-gated (Request Access, then a verification that takes roughly 3–5 business days). ServiceTitan tells customers not to give third-party developers admin access or API keys, and to contact ServiceTitan Integrations first. Plan for this before you quote. verified
- Business SMS (US): requires A2P 10DLC brand and campaign registration, with sample messages, a verifiable opt-in flow, and opt-out language. Since June 30, 2026, new campaigns must include public privacy policy and terms URLs, and the privacy policy must say mobile and consent data isn't shared for marketing. A sole-proprietor campaign is limited to one number. verified
Check what the app already does first:
- Jobber includes automated quote follow-ups, visit reminders, on-my-way texts, invoice follow-ups, and Google review requests with up to two reminders verified.
- Housecall Pro includes scheduled, on-my-way, finished, appointment-reminder, and invoice-reminder notifications verified. Review features: not verified.
- ServiceTitan native texting, on-my-way, and review features (reportedly tied to paid modules): not verified.
Build steps
- Audit the app's notification settings: scheduled, reminder, on-my-way, finished, invoice reminders, quote follow-ups, and review requests.
- Turn on the ones that fit, and rewrite templates in the owner's voice.
- Set cadences (for example, invoice reminders 1, 7, and 14 days after the due date).
- Register texting where the app requires it (Housecall Pro requires text-messaging approval before SMS notifications).
- Only build custom (for example an LLM reply classifier) when there's a measured gap.
Test cases before go-live
- Test job: every enabled notification fires once, with the correct variables.
- Paid invoice: reminders stop.
Tool names are examples, not endorsements. Check current features, plan tiers, and pricing before quoting a client.
Sample prompt
Rewrite this default notification template in a friendly, plain voice for {biz}, keeping all variables intact: {template}.Pitch it to the owner
"You're already paying for these features. We switch them on and make them sound like you."
Lead with the outcome, not with "AI," and show the business case using their own numbers.
What can go wrong
- Over-messaging customers. Keep cadences modest.
- Texting consent: Under the TCPA, automated texts generally need prior express consent, and marketing texts need prior express written consent. Honor STOP right away and keep consent records.
- Twilio/10DLC (2026): new A2P 10DLC campaigns must include public privacy policy and terms URLs (required since June 30, 2026), a verifiable opt-in, and opt-out language. Third-party lead generation and affiliate marketing are forbidden use cases. verified
- Reactivation defaults to email. Texting past customers is marketing. Use SMS only where written consent is documented.
- Call-recording consent: some states, including California, require all parties to consent (this list is not exhaustive). The safe default is to disclose recording and the automated assistant at the start of every call.
- AI voices: the FCC's February 2024 declaratory ruling (FCC-24-17) treats AI-generated voices as 'artificial voice' under the TCPA, so outbound AI calls generally need prior express consent. Further AI disclosure rules were only proposed in 2024. Keep builds inbound unless counsel approves. verified
- Failure modes: hallucinated details, missed escalations, and integrations that break silently. Add a human fallback, daily error alerts, and a weekly transcript review.
Not legal advice. Texting, calling, and recording rules vary by country and state and change over time. Have the client confirm compliance with qualified counsel before launch.
Suggested price
$300–$900 one-time setup service
Starting estimate only, not verified against market rates. Adjust for scope and support.