Lofty
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | CRM | Enter your Lofty account details in bubbl3 |
Lofty isn't offered yet. This page says what it will do and what you can use meanwhile: a Lead URL, or Zapier, Make or n8n.
What it does
Lofty is a CRM for real estate teams. Connecting it lets bubbl3:
- import every lead your key can see, with Lofty's real estate details (buyer or seller, source, stage, price range, location and time frame) kept on the contact, and check for changes every five minutes;
- log every text bubbl3 sends or receives, and held or refused texts with the reason, as notes;
- keep opt-outs in step through bubbl3's tag, Opted out of texts (bubbl3);
- update tags and lead details (name, stage, source, lead type, time frame) when a workflow or conversion event asks.
bubbl3 never sends Lofty's own texts, emails or smart plans.
Setup
- In Lofty, open Settings, Integrations, API and copy your key.
- In bubbl3, open Settings, Integrations, choose Lofty and paste the key. bubbl3 checks it with one read call.
- Check the count and the field mapping, and import.
- Answer How did these leads agree to hear from you?
| What you enter | Where to find it |
|---|---|
| API key | In Lofty, Settings, Integrations, API |
Disconnect
Disconnect from the connection page in Settings, Integrations.
- Stops at once: imports, the five-minute check, notes and writebacks.
- Deleted at once: your API key and the links between bubbl3 contacts and Lofty leads. Opt-outs still waiting are dropped.
- Kept: contacts imported from Lofty, with their messages, labels and consent, unless you tick Also delete the contacts imported from it. Notes and tags bubbl3 wrote stay.
- Deleted later: the changes bubbl3 read are deleted 30 days after they were read.
Data shared
From Lofty to bubbl3: leads' names, emails, phones, assigned agent, tags, and the real estate details above.
From bubbl3 to Lofty: notes for texts; the opt-out tag on STOP; tags and lead details when you ask.
Scopes and permissions
Lofty API keys have no scopes: the key sees what your Lofty user sees.
Events
What bubbl3 receives
| Event in Lofty | In bubbl3 |
|---|---|
| A new lead, found by the five-minute check | New contact. Imported and matched on phone and email; starts "Lead imported from CRM" workflows. |
| A changed lead, found by the five-minute check | Contact updated. Changes are applied; starts "CRM contact updated" workflows. The opt-out tag opts the lead out. |
What bubbl3 writes back
| What | Where it shows in Lofty |
|---|---|
| Text log | A note on the lead |
| Opt-outs | The tag Opted out of texts (bubbl3) |
| Field updates | The lead detail you chose |
| Tags | Tags added or removed |
| Notes | A note from a conversion event |
Sending rules that still apply
Lofty never texts anyone through bubbl3 itself. Its new and changed contacts can start your workflows, and every workflow text goes through the same checks as a text you send from bubbl3. Nothing in Lofty can turn them off.
- Consent. When you connect Lofty or create a lead source, you confirm that everyone you send to bubbl3 has agreed to receive texts from you, so its contacts can be texted straight away. bubbl3 never texts a contact who opted out, and a workspace set to text only opted-in contacts texts only them.
- Opt-out. Replying STOP opts a contact out at once. bubbl3 also records it in Lofty.
- Quiet hours. No texts from 8:00 PM to 9:00 AM in the contact's own time zone (from the phone's area code). A text due then waits until the morning.
- Pacing. Each line texts at most 15 new contacts an hour and 50 a day (fewer while a new line warms up), and spaces texts 20 to 90 seconds apart. A big import or batch is queued and sent as the limits allow, never dropped.
- First messages. Until a contact replies, a text can't include links, photos or files, phone numbers or email addresses, must be 300 characters or fewer, and at most 3 texts go out.
What Lofty is told when bubbl3 doesn't send
A note on the lead says the text wasn't sent, with the reason. A held text gets a note saying when it's scheduled.
| Reason | Code | What you see |
|---|---|---|
| A link before the contact replies | pre_reply_link_blocked | Not sent: "Links can't be sent until the contact replies" |
| A photo or file before the contact replies | pre_reply_media_blocked | Not sent: "Photos and files can't be sent until the contact replies" |
| A phone number before the contact replies | pre_reply_phone_blocked | Not sent: "Phone numbers can't be sent until the contact replies" |
| An email address before the contact replies | pre_reply_email_blocked | Not sent: "Email addresses can't be sent until the contact replies" |
| A first message that is too long | pre_reply_too_long | Not sent: "First messages must be 300 characters or fewer" |
| Too many texts without a reply | pre_reply_message_limit | Not sent: "Already sent 3 texts without a reply. Wait for the contact to reply" |
| The same text to too many people today | identical_text_limit | Not sent: "This exact text went to 20 people from this line today" |
| The line is paused after unanswered texts | unanswered_streak_limit | Not sent: "This line is paused after too many unanswered texts" |
| The contact opted out | contact_opted_out | Not sent: "The contact opted out of texts" |
| The workspace texts only opted-in contacts | consent_required | Not sent: "This workspace only texts contacts who opted in" |
| No line can reach the contact | line_unavailable | Not sent: "bubbl3's line for this contact isn't available" |
| Quiet hours | quiet_hours | Held: "Scheduled for 9:00 AM America/Chicago, quiet hours" |
| The line's daily limit | daily_new_contact_cap | Held: "Scheduled for Oct 15, 9:00 AM America/Chicago: today's limit for this line is reached" |
| The line's hourly limit of new contacts | hourly_new_contact_cap | Held: "Scheduled for 2:00 PM America/Chicago: this hour's limit of new contacts for this line is reached" |
The numbers are the default limits; a line's own limits change them. bubbl3's other checks (no phone number, a number that doesn't match) have their own plain reasons.
Limits and known gaps
- Lofty doesn't publish a request limit; bubbl3 makes at most 2 calls a second and 20,000 a day per connection.
- Lofty has no webhook bubbl3 can register, so changes arrive within about six minutes.
- bubbl3 texts the lead's first phone number; Lofty doesn't mark which one is a mobile.
- Imports take every lead the key can see: filters aren't offered.
Troubleshooting
- The connection needs attention. The key stopped working in Lofty. Paste a new one.