Troubleshooting

The problems people actually hit, and the fix for each. Ordered by how often they come up.

Nobody is getting called back

Check speed to lead is on. Automations → Speed to lead. It is off until you turn it on.

Check the lead actually arrived. Open Leads. If the person is not there, the problem is upstream: your form is not connected. See Bring in your leads.

Check the time. Automated outbound is held to 8am–6pm in your configured timezone. A form at 11pm gets worked in the morning, on purpose. See Availability.

Calls come in but never book

Almost always your calendar, not your script.

Open Availability and look at four things:

1. Minimum notice: if it is four hours, nobody books this afternoon
2. Maximum per day: if it is two, the third caller hears nothing available
3. Your hours: narrower than you think, especially the day you half-work
4. Blackout dates: an old vacation you never removed

Then check Google Calendar. If you connected the wrong calendar, LeadBind sees phantom busy time.

Only after all of that, look at your script.

Texts are not sending

Are you registered? Business texting requires A2P registration and unregistered messages are silently filtered, not bounced. See A2P. This is the cause the overwhelming majority of the time.

Is the number opted out? A STOP reply is permanent and deliberate. It will not send, and that is correct.

Is it outside 8am–6pm in your timezone? It will send in the morning.

Appointments land at the wrong time

Your timezone is wrong. Availability → Timezone. This one setting drives what is offered, what is read back, and when texts go out.

Or Google Calendar is set to a different timezone than LeadBind. Make them match.

Double-booked

Google Calendar is not connected, or you connected a calendar you do not actually use. Without it LeadBind only knows about its own bookings. See Availability.

Or you booked something manually elsewhere after the slot was offered. Buffers help; nothing fully prevents this except having the calendar connected.

The assistant said something wrong

It quoted a price. It should not and does not. If a price is in your script, take it out.

It got your business wrong. Check the business name in Branding and the description in Studio.

It did not know something obvious. Add the question and the answer to your script. It only knows what you told it.

Somebody says they never asked to be contacted

Stop and take it seriously.

1. Add them to your do-not-contact list immediately. A STOP reply does it automatically; anything else you do by hand.
2. Find out where the lead came from. The lead record shows the source.
3. If the source is a purchased or scraped list, stop using it. See Consent and opt-outs. This is the one on this page that costs real money if you ignore it.

My AI assistant cannot see LeadBind

"Invalid or missing API key": the key is wrong, revoked, or missing the word Bearer in front of it.

"This key lacks the 'write' scope": read-only key, write request. Make a new key. Keys cannot be upgraded, deliberately. See Keys and permissions.

No tools at all: restart the app. Most read MCP config only at startup.

It booked a time you are not free: it guessed instead of checking availability. Tell it to check first, and verify your hours are right.

Still stuck

Get help. Include your account email, what you expected, what happened, roughly when, and the phone number involved.