Connecting Leads to ClientTether
Five routes a lead can take into the system, how to choose between them, and the four things every route has to get right.
On this page
1Five ways in
A lead is only worth having if it reaches ClientTether fast enough to act on. There are five routes in, and most businesses use several at once. This page helps you pick the right one for each source.
| Route | Use it when | Effort |
|---|---|---|
| Web Forms & the Web Key | The lead comes from your own website — a hosted form, an iframe, a JavaScript form or a plain POST. | Minutes. |
| Hosted Pages | You want ClientTether to host the form, the scheduler or the chatbot for you. | Minutes. |
| Built-in integrations | The source is a marketplace or platform ClientTether already supports — Thumbtack, Angi, ClubReady, Hireology. | Credentials and a lead source. |
| Email Parser | The source can only send an email. | An hour of bookend work per sender. |
| API (or Zapier) | Your own system, or an app with no built-in connection. | Development work. |
2What every route needs to get right
- A lead source, so you can tell later which channel paid for itself.
- A Connection Plan attached to that source, so follow-up starts on arrival rather than when someone notices.
- Duplicate checking, so a returning enquiry updates the contact instead of splitting their history.
- Texting consent captured honestly on the form — see Texting (SMS).
Speed is the whole game
Marketplace leads go to several businesses at once. A Connection Plan whose first step is an immediate text beats a plan that waits an hour, every time.
3Lead generation requirements
Consent rules for contacting leads have tightened: a form that collects a phone number and implies you’ll text it must say so, explain how to opt out and link to a privacy policy. This isn’t only good manners — it’s what your carrier registration is judged on. See Telephony & Texting Registration.
4Checking it works
Submit a test lead through each route and confirm three things: the contact was created, the lead source is right, and the Connection Plan started. Then check the API Monitor in the user menu for anything that was rejected.