Connections

Connect the tools your team already has open. Ten of them, on the web and on the phone.

Manage them at Connections on the web (under Reach in the sidebar, or in the Menu on a phone), or at Settings, then Lead sources and integrations on the web or in the iPhone app. The page has the same name everywhere it is linked: the sidebar, the Menu, Quick Find and the card Mani shows when she offers to open it. Both surfaces read the same list, so a tool you connect on one is connected on the other.

What you can connect today

• Slack: New leads and missed calls posted to the channel your team already watches.
• Discord: New leads and missed calls posted to the channel your team already watches.
• Notion: Leads and call summaries written into your Notion workspace.
• HubSpot: Contacts and call outcomes synced both ways with your HubSpot pipeline.
• Airtable: Leads written into the base you already run your pipeline in.
• Google Calendar: Booked jobs land on your calendar automatically, and busy time blocks new bookings.
• Calendly: Your existing Calendly bookings show up beside the ones your front desk books.
• Zoom: Every booking gets a real Zoom link attached, created on your own account.
• Google Meet: A Meet link on every booking, created on the calendar event itself.
• Google Drive: Documents your front desk can read when a lead asks about something you have on file.

Telegram is connected separately, from the same screen, for one-to-one alerts rather than a team channel.

Ad platforms that are delivering leads (for example Meta lead ads, once a real lead has arrived) are listed here too, so the count at the top matches the Ad platforms page. Connect a tool adds a tool your business already uses that offers a server for assistants, so Mani can use what it does.

Two ways in, and why you can always use one of them

Most of these offer a normal sign-in-and-approve flow. Every one of them also accepts a credential you create yourself and paste in, which matters more than it sounds: the paste path never depends on us having registered an application with that vendor, so it works the day you need it rather than the day we get around to it.

The screen tells you which fields that tool wants, where to create the credential, and exactly what the credential can reach. Those instructions come from the same place on both platforms, so the phone is never behind the web.

We check the credential before we say you are connected. It is used against the real service once, on the spot. If the token is wrong, or the scope you granted is not the one the job needs, you get that tool's own words back rather than a green tick that means nothing.

What a connection can actually reach

Narrower than people expect, and deliberately.

A Discord webhook can only post into the one channel it was made in. It cannot read your messages, see your other channels, or act as a member of your server. Slack posting needs only chat:write, and channels:read on top of that only if you want us to list your channels for you.

Each tool's screen states its own scope note before you connect. Read that line. It is the honest description of what you are handing over, and it is written per tool rather than as one blanket paragraph.

Disconnecting

Disconnect from either surface, web or phone, and it takes effect immediately. LeadBind asks first. If the disconnect does not go through, the screen says so and the tool stays connected, so try again rather than assuming it is gone. We drop the credential. If it was a token you created, revoke it on the vendor's side too, the same way you would with any key you had issued.

If the tool you want is not here

Tell us. The list is ordered by what customers actually ask for, and adding one is small work once someone has asked. There is also a general path: see Carrier connect for logging into a portal we do not have a direct integration with.