Configurable CRM webhook
Send qualified seller details to a compatible public HTTPS endpoint. Push manually or enable auto-push after your team qualifies a conversation.
CRM handoff and data portability
Keep seller context moving with the deal.
Connect a qualified lead to your next workflow, bring in a CSV and take your data with you. See what connects today and how to set it up.
Available connections
A practical connection at each step.
Some connections are managed by TBP. Your outbound CRM handoff is configured for the receiving workflow you choose.
CSV list import
Import up to 5,000 rows at a time. Map supported contact and property fields, skip unwanted columns and review duplicate or invalid rows.
Four CSV exports
Download seller leads, contacts, campaign results or inbound and outbound message history. Export access follows workspace permissions.
Configured SMS provider
Approved sending numbers connect through TBP's configured messaging provider. Incoming messages and delivery updates depend on the provider connection and its webhooks.
Payments through Stripe
Use Stripe-backed billing for your subscription and a separate Stripe checkout for Order Data. Manage payment details through the account billing flow.
Branded transactional emails
Verification, password reset, team invitation and setup emails use TBP's configured email service. These are account emails, not a customer email-campaign builder.
Qualified lead to CRM
Keep the handoff close to qualification.
Once your team has a lead worth working, send its details into the receiving workflow without copying every field by hand.
- Start with a receiving workflow
Use a CRM, automation tool or custom receiver that accepts an HTTPS webhook. Configure its field mapping and actions on that system.
- Connect and test inside TBP
Enter the public HTTPS URL in integration settings. Test the connection and optionally add signing so your receiver can verify requests.
- Choose when the lead is sent
Push manually from a seller record, or enable auto-push after manual qualification. Automatic handoff does not mean automatic lead qualification.
- Send the context, not just a phone number
The supported payload includes contact and property details, qualification information, campaign context and assignee details.
Know the boundary
An outbound handoff, not a two-way CRM sync.
TBP sends a structured lead payload to your configured endpoint. The receiver handles its own mapping and actions. TBP does not offer native two-way Podio synchronization or a general-purpose public customer API.
If your workflow uses Podio, Zapier, Make or another tool, tell us the exact handoff you need. A compatible receiver may connect it, but that does not make every connector or action a native TBP feature.
Discuss my workflowBuild around the right workflow
Plan the handoff before your first campaign.
Prepare your workspace during the seven-day setup trial. Live SMS requires eligible paid billing and approved messaging setup.