Microsoft Dynamics 365
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | CRM | One click: approve bubbl3 on Microsoft Dynamics 365's own page |
Microsoft Dynamics 365 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
Connecting Microsoft Dynamics 365 (Dataverse) lets bubbl3:
- import open Leads and Contacts (both, one kind, a saved view, an owner, or those changed since a date) and check for new and changed rows 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 a Yes/No column you add;
- update fields when a workflow or conversion event asks.
bubbl3 never writes Dynamics' own "Do not allow phone calls" and never runs Dynamics workflows, emails or SMS.
Setup
You need a work account in your company's Microsoft tenant. Your Microsoft admin may need to approve bubbl3 for the tenant first.
- Recommended: ask your Dynamics admin to add a Yes/No column whose logical name ends in
bubbl3smsoptout(any publisher prefix) to Lead and to Contact. - In bubbl3, open Settings, Integrations, choose Microsoft Dynamics 365, then Connect, and sign in on Microsoft's page.
- One environment connects straight away. If you have several, pick each environment to connect.
- Choose what to import, check the count and the field mapping. Mobile is the number texts go to, then business phone.
- Answer How did these leads agree to hear from you?
Disconnect
Disconnect from the connection page in Settings, Integrations.
- Stops at once: imports, the five-minute check, notes and writebacks.
- Deleted at once: bubbl3's tokens and the links between bubbl3 contacts and Dynamics rows. Opt-outs still waiting are dropped.
- Kept: contacts imported from Dynamics, with their messages, labels and consent, unless you tick Also delete the contacts imported from it. Notes and values bubbl3 wrote stay.
- Deleted later: the changes bubbl3 read are deleted 30 days after they were read.
Data shared
From Dynamics 365 to bubbl3: Leads' and Contacts' names, email, mobile and business phone, owner, company (Leads), "Do not allow phone calls" and the opt-out column; your environments' names.
From bubbl3 to Dynamics 365: notes for texts; the opt-out column on STOP (or a note saying so when the column doesn't exist); fields when you ask.
Scopes and permissions
| Scope | Why bubbl3 needs it |
|---|---|
openid | Identify your tenant |
offline_access | Stay connected without signing in again |
https://globaldisco.crm.dynamics.com/user_impersonation | Find your Dynamics environments, then read and write Leads, Contacts and notes as you |
Events
What bubbl3 receives
| Event in Dynamics 365 | In bubbl3 |
|---|---|
| A new Lead or Contact, found by the five-minute check | New contact. Imported and matched on phone and email; starts "Lead imported from CRM" workflows. |
| A changed Lead or Contact, found by the five-minute check | Contact updated. Changes are applied; starts "CRM contact updated" workflows. The opt-out column set opts the contact out. |
What bubbl3 writes back
| What | Where it shows in Dynamics 365 |
|---|---|
| Text log | A note on the Lead or Contact |
| Opt-outs | The bubbl3smsoptout column set to Yes, or a note when it doesn't exist |
| Field updates | The column you chose |
| Notes | A note from a conversion event |
Sending rules that still apply
Microsoft Dynamics 365 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 Microsoft Dynamics 365 can turn them off.
- Consent. When you connect Microsoft Dynamics 365 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 Microsoft Dynamics 365.
- 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 Microsoft Dynamics 365 is told when bubbl3 doesn't send
A note on the record 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
- A two-option column as the consent field opts out everyone set to No. If you choose "A field in the CRM records it" and name a Yes/No column, every record left at its default No reads
falseand is opted out in bubbl3 (not copied to your other CRMs). Name a column that's empty until someone answers. - Changes arrive within about six minutes, not instantly.
- Import previews stop counting at 5,000 and say "at least".
- Tags, stages and pipelines aren't import filters; use a saved view.
- Government cloud environments can't connect yet.
Troubleshooting
- Microsoft says an admin must approve bubbl3. Ask your Microsoft admin to grant consent for your tenant, then connect again.
- Opt-outs show as notes. The
bubbl3smsoptoutcolumn is missing on Lead or Contact. - The connection needs attention. Microsoft refused to renew bubbl3's access. Reconnect.