Calling and texting rules that run as checks in the software, with the limits stated.
Calling and texting rules are easy to write in a policy and easy to forget on a busy Tuesday. LeadBind runs the ones it can see as checks before a call or a text goes out. This page lists each one, the place it applies, and the places it does not. You decide who to call and you hold the consent. This page describes what the product does. It is not legal advice.
What runs before a call or a text goes out.
Five checks, one line each. The detail and the limits follow.
Calls and texts follow the lead's clock
The automatic dialer, batch runs and campaigns call only between 9 a.m. and 7 p.m. in the lead's own time zone, which sits inside the 8 a.m. to 9 p.m. hours the federal calling rules allow. Every other AI call, and every text, including one typed by hand unless it answers the contact's own text from the last day, is held to 8 a.m. to 9 p.m. in the lead's time zone.
Do not call is checked first
Every call to a saved lead is checked against your do-not-call flags and your own suppression list before it dials. A lead who texted STOP is on that list, and so is one who asked on a call to stop being called.
No consent on file, no AI call
The automatic dialer and saved-lead calls skip any lead with no recorded consent. Consent is recorded when a lead opts in, when you attest to a whole list, or when you confirm it for one number before an AI call to it.
Texting waits for registration
No customer text goes out until the account's own carrier registration clears, and a reply of STOP works at once.
Your AI tools get three separate permissions
Read, write and dial are separate. A key that can read and write cannot place a call, and every tool call is logged where you can see it.
The checks that run before a call goes out.
These apply to AI calls, whether the automatic dialer, a batch run, a campaign, an instant call-back or a single call placed by you or your AI tool places them. The limits at the end of the section say where they do not apply.
Their time zone, not ours
LeadBind works out where the lead is from the state on the lead record, or from the area code of the phone number, and calls only between 9 a.m. and 7 p.m. there. The legal band is 8 a.m. to 9 p.m. The tighter window is on purpose: a one hour mistake about a time zone still lands inside the legal band. A call that is too early is held and tried when the window opens.
Three do-not-call lists, checked before every call
Your leads marked do-not-call, your own uploaded suppression list, and a shared suppression list that applies to every account. A hit is written back to the lead with the time and the reason, so it is not tried again.
Consent is checked per lead
A lead can be called by the AI only with a recorded consent time, from an opt-in form or a booking, or with a list attestation you signed. The attestation records who signed, when, the exact wording version and how many contacts it covered. Leads added to the list later are not covered until you attest again, and consent never overrides a do-not-call. An AI call to a number that is not a saved lead is refused unless you confirm the person agreed, and that confirmation is recorded with who gave it and when before the call is placed. A new lead from a form, an ad or a vendor counts as consented only when what was sent says so.
Consent-only mode
Turn on consent-only mode and the dialer takes only leads with a real recorded consent time. The list attestation shortcut is switched off, and a call to a bare phone number with no saved lead is refused.
The dialer starts switched off
Automatic dialing is off until you turn it on. To turn it on you attest that your leads gave prior express consent or are an existing customer, and a self-serve account must also be in consent-only mode. Withdrawing the attestation switches dialing back off.
A daily cap, a retry limit and no double dials
You set a daily cap on how many leads the dialer calls, from 0 to 500. A lead that has been tried 5 times is dropped from the automatic dialer. Each lead is reserved before its call is placed, so two overlapping runs cannot dial the same person twice.
Every voice agent is told to disclose first
The first thing every LeadBind voice agent is instructed to say is that the line is recorded and that it is a virtual assistant. It is instructed never to claim to be a person. That instruction sits in a locked block of the agent's prompt that an account cannot edit away. It is an instruction to the agent, not a filter on the audio.
One call at a time is held to the clock too
A single AI call, from the dial button or from a connected AI tool, goes out only between 8 a.m. and 9 p.m. in the lead's own time zone. Outside those hours it is refused with the time the window next opens.
Instant call-backs use the lead's clock and your full list
When a new lead arrives and the account is set to call back at once, the call goes out only with consent from the source, after the full do-not-call check, and only inside both your calling hours and 9 a.m. to 7 p.m. in the lead's own time zone. Outside those hours the lead is queued for when its window opens.
A spoken stop request is honored
When the person on a call clearly asks to stop being called, to be taken off the list or to be put on a do-not-call list, LeadBind adds the number to your suppression list and marks the lead do-not-call when the call ends, and stops any follow-up that call would have started. It reads only what the other person said, and only clear requests count, so "call me back Friday" is not one.
- The National Do Not Call Registry is not checked
LeadBind does not look numbers up on the National Do Not Call Registry. That is why a self-serve account can turn the dialer on only in consent-only mode. If you call people who have not consented, scrubbing against the registry is yours to do.
- Consent is recorded, not verified
LeadBind records the consent time or the attestation you give it. It cannot see how the consent was collected, so it cannot confirm it.
- Time zones are an estimate
A phone number can travel with its owner, so the lead's zone is a good estimate and not a fact. Where a state spans two zones, the 8 a.m. to 9 p.m. band has to hold in both, so a Texas lead is not called before 9 a.m. Central. When neither a state nor an area code resolves, LeadBind assumes Central time.
Registered before the first text, and STOP means stop.
Texting has its own gate, separate from calling.
No registration, no texts
Customer texts go out only on the account's own carrier registration. Until it clears, a send is refused with a plain reason. They are never sent on a registration shared with other accounts.
STOP works at once
A reply of STOP, STOP ALL, UNSUBSCRIBE, CANCEL, END, QUIT, OPT OUT, REVOKE or REMOVE marks the lead do-not-contact and adds the number to your suppression list, so the AI dialer and every text path skip it from then on. The person gets one confirmation message, and never a second one for a repeat STOP. Only a message that is exactly one of those words counts, so "stop by my office" is not an opt-out.
Follow-up texts wait for 8 a.m. to 9 p.m.
Automated follow-up texts and appointment reminders are held outside 8 a.m. to 9 p.m. in the lead's time zone and sent when the window opens. They are deferred, not dropped.
Do-not-contact and consent are checked on every send
Every text is checked against the do-not-contact flags and suppression list first. A text typed by hand in the inbox gets "Reply STOP to opt out" added if it is missing, and in consent-only mode a text to a lead with no consent is refused. Inbox texts are limited to 20 a minute per account, and the limit fails closed.
A text typed by hand waits for the hour too
A text a person types in the inbox, or one the assistant sends after you approve it, goes out only between 8 a.m. and 9 p.m. in the contact's time zone. The one exception is a reply to a text that contact sent in the last 24 hours, because that is a conversation they started. Outside those hours the send is refused with the time the window next opens.
What an AI connected to LeadBind can and cannot do.
Claude, ChatGPT, Cursor and any other AI that speaks MCP reach LeadBind through one endpoint with a key or a sign-in. The tool list and the setup steps are on the developers page.
Three permissions, dial on its own
A key carries read, write, dial or any mix. Read looks and changes nothing. Write changes the account. Dial places a real call. Dial is never implied by write. A tool the key cannot use is hidden from the AI and refused if it tries. A key that can dial can only be created on an account with an active plan, and signing in through your AI tool's own login starts as read only.
Per-minute limits on every key
Each key is limited to 240 read calls, 60 write calls and 10 dial calls a minute. The dial limit fails closed: if the limiter itself breaks, the call is blocked rather than allowed. Placing a call has a second limit of 10 a minute per account underneath.
A call from an AI runs the same guards as a call from you
The place_call and run_list tools use the same code as the portal's own dial button: plan and billing, voice entitlement, the outbound plan, consent, do-not-call, and the lead's own 8 a.m. to 9 p.m.. A bare phone number needs the AI to state consent: true, which is recorded with the key that sent it. run_list, which calls a whole list, also holds each lead to 9 a.m. to 7 p.m. their time and stops at your daily cap. A blocked lead comes back with the reason instead of being forced through.
A retry does not call twice
When the AI sends an idempotency key with a write, a retry with the same key returns the first result instead of doing it again. A dry run describes what would happen and places nothing.
Booking needs the customer's yes
The booking tool refuses unless the AI states the customer agreed to be contacted, and the booking page checks the same rule on its own.
Recordings and transcripts never leave
No tool returns a call recording, a transcript or an audio link to an AI. A filter on the way out removes them even if a tool tried to include one. Lead names and numbers, and the short written summary of each call, are shared with the AI provider you chose, and you acknowledge that when you create a key.
No tool sends texts or emails, or deletes your records
There is no AI tool for sending a text or an email, and none that deletes leads, calls or appointments. Booking an appointment can trigger the customer's confirmation, the same as when they book it themselves. No tool changes a key's permissions. You do that in your account.
You can see what your AI did
Every tool call is recorded with the tool, its permission, whether it worked, how long it took and which credential made it, and you can read that list in your account. The details of what it sent, such as a lead's name or number, are not copied into that log.
Yours to export, yours to delete, and a record of what happened.
What you can take, what you can remove, what we keep and what we write down.
Export your leads and appointments
You can download your leads and your appointments as CSV files from your account at any time. An organization owner exports the whole organization.
Delete your account
Deleting your account signs out every session at once, cancels the subscription, releases your phone numbers, revokes calendar access at the calendar provider, and permanently deletes your leads, lists, drip sequences, API keys, notifications and suppression list. Call records and text history are kept for billing and legal records, and the account row is kept with your personal fields scrubbed.
Keys are stored as a fingerprint
A key is shown once and only a one-way fingerprint is stored, so it cannot be read back, even by us. You can revoke a key at any time and it stops working at once. An account can hold 10 active keys at a time.
What is written down
Each do-not-call mark keeps its time and reason. Each lead keeps when and how its consent was recorded, and an AI call to a number that is not a saved lead keeps who confirmed consent and when. Your dialing attestation keeps its time. A key keeps which version of the data-sharing notice you accepted, and when. Calls keep their outcome, and their recording and transcript are shown to you on the call page.
Quiet hours for your own alerts
Alerts that buzz your phone, which are push, Telegram and text, are held between 9 p.m. and 8 a.m. in your own time zone unless you change it or turn it off. A live transfer, a callback you set yourself and real-time alerts such as a new lead still ring through. Email is never held.
We do not sell personal information
The privacy policy says it in one line, and it is the policy that governs this data.
Plain statements, each one checkable.
Each line below is backed by the same kind of check as the rest of this page.
- We do not check the National Do Not Call Registry.
See the limit under Calls.
- We do not verify how your consent was collected.
We record what you attest to.
- We do not let a read or write key place a call.
Dial is its own permission.
- We do not hand recordings or transcripts to an AI tool.
A filter removes them from every tool response.
- We do not send your customers' texts on a registration shared with other accounts.
Each account texts on its own.
- We do not keep a readable copy of your API keys.
Only a fingerprint is stored.
- We do not sell personal information.
Per the privacy policy.
- We do not promise that your calling or texting is legal.
You choose who to contact and you hold the consent. LeadBind runs the checks above and shows you the result.
Signed in, the Compliance page shows the live state of your account: your calling hours, whether consent-only mode is on, your suppression list and your texting registration. A piece that is not set up reads as not set up, never as a pass.