Separate saved configuration from a working action
A connection brings together several decisions: which business account owns the data, which operation is intended and which provider permissions allow it. Saving settings records configuration. It does not by itself confirm provider access, activate automation or establish that an export, booking or message has completed.
Sign in as the business account owner and open Business connections. Select the intended provider card, review the requested account permissions through Connect account and authorize the account your business owns. Use Advanced token setup only for the supported manual path. Keep credentials in the configuration flow rather than placing them in agent instructions, reference documents or a conversation.
Check the destination and mapping
For a CRM handoff, inspect the lead or contact fields, stage and owner mappings before exporting. For a calendar action, check the selected calendar, appointment details and the intended account. The connection should match the workflow you reviewed, rather than an unrelated account that happens to be available.
Calendly uses its configured event type and supported provider access. Booking needs the invitee details required by that operation, including an email address. Rescheduling uses the provider-hosted link; review the resulting change against the linked appointment. A requested booking and a confirmed provider appointment are distinct outcomes, so inspect the receipt and provider record before telling someone the appointment is complete.
Keep messaging permission and reading access separate
Email and WhatsApp each require their own channel setup and recipient permission. Customer-created messages retain their consent, plan and credit requirements. Permission to call a number does not establish permission to send it a message, and importing a contact list does not grant either permission.
In Message automation, the WhatsAppMate integration uses a reviewed owned sender and approved templates. Reading preferences use a separate read-only key with selected scopes; a sending key does not grant inbox access. Import one latest page is an explicit incoming-text import and does not send a message or charge messaging credits. Review provider acceptance, delivery status and a recipient reply as separate observations.
Use the receipt to decide the next step
After an operation you deliberately choose, inspect the exact receipt and the corresponding provider record. Pending, conflicting, failed and uncertain states require review; they are not completion confirmations. For an uncertain result, keep the existing request evidence and use the supported reconciliation path rather than creating another request that might duplicate the action.
Automatic lead exports and incoming calendar changes have separate preferences. Review the account, acknowledgement and execution status for each preference. Notification permissions are separate from base calendar access. Disabling a preference cancels waiting work where supported, while an already admitted action may finish. Check the retained receipt before retrying or changing settings. Telephone calls also keep their own eligible-number, recipient-permission and funded-admission checks.