Does submitting this start texting my customers?
No. This is a setup intake only. Customer-facing texts require approved wording, consent handling, carrier registration, testing, and written go-live approval.
The Catcher setup intake
Walk us through what happens when your team misses a call. Building Jarvis uses this to prepare the text-back wording, callback rules, and human-escalation plan for your approval.
Local setup intake only. This page does not send texts, create HighLevel records, or connect to your phone system.
What this setup intake does
This form collects the plain-English rules Building Jarvis needs to plan The Catcher: who the business is, what happens today when a call is missed, what the text-back should sound like, and what must always go to a human.
It does not authorize customer messaging. It does not connect to HighLevel. It does not register a number. Those steps happen separately, in writing, after review and approval.
Local-only intake
No texts go out until you approve the wording, rules, and launch steps.
No. This is a setup intake only. Customer-facing texts require approved wording, consent handling, carrier registration, testing, and written go-live approval.
No. Do not share passwords, API keys, OAuth logins, exports, or customer records in this form. Live access is arranged separately, in writing.
No. Pricing, availability promises, emergencies, complaints, and unusual requests should route to a human unless a specific rule is approved.
No. It creates a faster, more organized response path for missed calls. It cannot guarantee booked jobs, revenue, or customer decisions.