Choose Twilio or SimpleTexting and configure SMS

Settings → Texting offers Twilio and SimpleTexting. Twilio is the more hands-on option: you manage the account, credentials, sending numbers, and messaging configuration. SimpleTexting provides a managed texting dashboard and onboarding support, typically at a higher cost. Neither choice is a guarantee of the lowest total cost.

Each company opens and pays for its own provider account. Provider subscriptions, message usage, phone numbers, and registration charges are separate from the Kinetic View subscription. Review your provider’s current charges against expected volume before selecting it.

Choose Twilio, then enter the Account SID, Auth Token, and Messaging Service SID where applicable. Configure your sending number, default number, and the required provider approvals. Save credentials through the protected settings screen, never in lead notes or a support message.

The existing Twilio workflow includes incoming-message webhooks. Use the webhook URL shown by the running CRM and verify it in the provider dashboard. A saved credential or active number is not proof that messages are deliverable.

SimpleTexting requires a paid account and completed business registration before its API token is available. Registration asks for your legal business name, EIN, how customers opt in, and sample messages. Complete this in your own provider account; do not put an EIN or API token in a CRM note or support chat. Open Integrations → API & Webhooks and request API access from support. The trial phone number is temporary; choose an approved sending number when activating the paid account.

After approval, choose SimpleTexting in Kinetic View Texting settings and save the issued bearer API token and approved sending number with country code. The integration uses API v2. Copy the private Incoming Message Webhook URL into SimpleTexting Integrations → API & Webhooks and select INCOMING_MESSAGE. Keep the token and webhook URL private.

Incoming-message webhooks bring verified replies into the CRM. Incoming email forwarding notifies selected active team members only when they have permission to read the conversation. STOP replies disable the matched lead’s CRM SMS consent. MMS, delivery-status callbacks, automatic number provisioning, and provider-dashboard campaigns are not connected by this integration.

Provider references: https://simpletexting.com/api/docs/v2/ and https://simpletexting.com/pricing/.

A valid phone number, enabled provider, and permission to text are separate requirements. Use an internal test contact who explicitly agreed to receive the message. Changing providers does not move a phone number or transfer approval automatically.

Do not infer permission from a phone number, imported contact, or lead form submission. Keep the opt-in context and honor opt-outs. The CRM stores SMS consent and its timestamp; verify provider and CRM opt-out behavior before launching automations.

Long messages and special characters can affect segments or provider limits. Review provider usage as well as CRM counters. A CRM monthly usage display is not a substitute for the provider’s bill.

Check the selected provider, approval/API access, credentials, sending number, customer consent, destination number, and error message. For SimpleTexting, also check your paid account, business registration, approved API access and available credits.

If a send appears successful but the phone has not received it, check the provider before retrying. Repeated sends can duplicate a customer message. Never share a token when requesting support; provide the error and approximate send time.