This article explains the SMS/MMS integration options available through Teklink-supported platforms, including ChatServ and SkySwitch messaging options.

This article focuses on messaging integrations only. For voice/call integrations such as call logging, call routing, webhooks, click-to-call, WebRTC, or AI voice applications, please refer to our separate phone system integration article.

Important Compliance Notice

SMS and MMS messaging is subject to carrier rules, registration requirements, acceptable use policies, opt-in/opt-out requirements, messaging limits, and filtering by receiving carriers.

If Teklink provides access to SMS/MMS functionality, API access, webhook options, or messaging enablement on a phone number, the customer is responsible for ensuring that all messaging activity complies with applicable messaging rules and requirements.

Customers must only send messages that are allowed under their approved messaging use case and must only send messages to recipients who have properly opted in to receive those messages.

Customers are also responsible for message content, recipient consent, opt-out handling, message frequency, and ensuring that messaging does not exceed limits set by carriers or messaging providers.

If messaging is used in a way that violates carrier rules, acceptable use policies, registration requirements, opt-in/opt-out requirements, or messaging limits, Teklink and its affiliated providers may suspend or disconnect SMS/MMS services. Violations may also cause numbers to be blocked, filtered, marked as spam, or otherwise restricted by carriers.

Teklink can help provide platform access and available documentation, but Teklink does not take responsibility for customer-created messaging workflows, API usage, message content, recipient lists, opt-in records, or compliance with the customer’s specific messaging use case.

ChatServ Messaging Platform

ChatServ is a standalone messaging platform available at:

https://sms.theteklink.com

ChatServ provides a web-based interface and backend for sending and receiving SMS and MMS messages. It can be used as the messaging platform for customers who need messaging outside of the standard phone system app, or for customers who need additional functionality beyond basic send/receive messaging.

ChatServ works from a browser. A mobile app is also available for conversations. Settings and advanced features are managed from the web app.

ChatServ is a standalone application. It does not run inside another softphone application and is not built into the phone system softphone interface.

ChatServ Carrier Connectivity

ChatServ can integrate with multiple messaging carriers. Teklink uses this carrier connectivity to enable SMS/MMS on phone numbers depending on the customer’s platform and messaging setup.

For some customers, ChatServ may be used as the primary messaging platform. For others, it may be used as a proxy, copy destination, or advanced messaging platform in addition to another messaging interface.

ChatServ Integration Options

1. Inbound and Outbound Message Webhooks

ChatServ can post message activity to a webhook.

Depending on the configuration, this can include:

• Inbound messages

• Outbound messages

• Both inbound and outbound messages

This can be useful when a customer wants message activity to trigger an action in a CRM, ticketing system, automation platform, or custom application.

Common use cases

• Create a ticket when a new inbound text message is received

• Log inbound messages in a CRM

• Trigger an automation when a message is received

• Send message activity to a custom dashboard or reporting system

• Keep another system updated with messaging activity

Limitations and considerations

• The customer must provide a system or endpoint that can receive and process the webhook data.

• The customer or their developer is responsible for processing the webhook, matching it to CRM records, and handling any automation logic.

• Teklink does not normally build, host, troubleshoot, or maintain the customer’s webhook processor or external integration.

2. Outbound SMS API

ChatServ can support sending outbound SMS messages through an API using API key authentication.

At this time, the API is for SMS. MMS API support is on the roadmap.

Customers who need API access should contact Teklink support for API information and to request an API key.

A full ChatServ API and feature knowledge base article is planned for the future. ChatServ is still completing additional advanced features, and full API documentation will be published once the platform and related documentation are considered complete.

Common use cases

• Send SMS messages from a CRM

• Send appointment or ticket updates from an external system

• Send notifications from a custom application

• Trigger outbound SMS from an automation workflow

Limitations and considerations

• API access must be requested through Teklink support.

• API keys must be stored securely by the customer or their developer.

• The customer is responsible for all messages sent through the API.

• API usage must comply with messaging registration, opt-in, acceptable use, and carrier requirements.

• Teklink does not normally build, host, troubleshoot, or maintain the customer’s external API integration.

ChatServ Advanced Messaging Features

ChatServ is more than a basic SMS/MMS inbox. It includes advanced messaging tools that may be useful for customers who need more than simple send/receive messaging.

Available or planned capabilities may include:

• Keyword responses

• Auto replies

• Office-hours-based rules

• Different replies during business hours and after hours

• Drip campaigns

• Reminders

• Message templates

• Workflows

• Mass messaging

• Additional advanced messaging automation features

Feature availability may depend on the customer’s account, configuration, and the current platform release.

Customers should contact Teklink support for current feature availability and pricing.

SkySwitch Messaging Options

SkySwitch provides messaging through the ConnectUC app. This allows users to send and receive messages directly through the SkySwitch/ConnectUC user experience.

For many customers, ConnectUC messaging is enough when the goal is simply to send and receive messages from the phone system app.

However, customers may need ChatServ instead of, or in addition to, ConnectUC when they need API access, webhook-based workflows, advanced messaging automation, keyword responses, drip campaigns, templates, or other advanced messaging features.

SkySwitch Direct SMS API

SkySwitch has API options for sending SMS, but this access is at the reseller level and may expose access across numbers on the account.

Because of this, Teklink cannot provide direct SkySwitch reseller-level SMS API access to customers.

If a SkySwitch customer needs API access for sending SMS, Teklink can set the customer up with ChatServ as a proxy to provide an API-based messaging option.

SkySwitch Inbound SMS/MMS Webhooks

For inbound SMS/MMS, SkySwitch can post inbound messages to a webhook.

If the customer only needs inbound message notifications, this may be configured through SkySwitch directly without using ChatServ as a proxy.

Common use cases

• Notify an external system when a new inbound message is received

• Create a ticket from an inbound SMS/MMS

• Log inbound SMS/MMS in another system

• Trigger a workflow when a customer sends a text message

Limitations and considerations

• This is mainly for inbound message handling.

• The customer must provide the receiving webhook endpoint and processing logic.

• Teklink does not normally build, host, troubleshoot, or maintain the customer’s external webhook processor.

SkySwitch with ChatServ

ChatServ can also be used with SkySwitch numbers.

A SkySwitch customer may use ChatServ when they need:

• API access for sending SMS

• Webhook-based messaging workflows

• Keyword responses

• Auto replies

• Office-hours rules

• Drip campaigns

• Reminders

• Templates

• Workflows

• Mass messaging

• A standalone messaging UI

• Advanced messaging features not available in the standard ConnectUC messaging interface

However, using ChatServ may increase the customer’s monthly cost because ChatServ is billed separately from the standard ConnectUC messaging interface.

Messaging Charges and Platform Charges

SMS/MMS charges may include multiple parts.

1. SMS/MMS enablement on the phone number

There may be a monthly charge to enable SMS/MMS on a phone number.

Message usage may also be metered. Teklink may include a monthly message grant, and additional message charges may apply once the included monthly grant is used.

These charges apply when the SMS/MMS portion of the number is enabled, regardless of which supported UI or integration is used.

2. Messaging platform access

There may also be charges for the platform used to access and manage the messages.

For SkySwitch customers, ConnectUC messaging is provided as the standard messaging UI.

ChatServ is a separate platform and may be billed per user. Each user who needs login access to the ChatServ UI may require an additional user charge.

Because of this, a SkySwitch customer who only needs basic send/receive messaging may not need ChatServ. ChatServ is generally used when the customer needs API access, webhook workflows, advanced messaging features, or a standalone messaging platform.

Customers should contact Teklink support for current pricing, available options, and account-specific setup requirements.

SkySwitch and ChatServ Routing Options

When ChatServ is used with SkySwitch, there are two main ways the messaging route may be configured.

Option 1: ChatServ as the Primary Messaging Destination

In this setup, ChatServ is the primary destination for inbound and outbound messages.

ChatServ handles the message flow, and messages can also be copied to ConnectUC so both ChatServ and ConnectUC can work at the same time.

The customer may also choose to use only ChatServ if they do not need the ConnectUC messaging interface.

Common use cases

• Customer wants ChatServ as the main conversation view

• Customer wants complete ChatServ conversation history going forward

• Customer wants ChatServ advanced features to work with full message context

• Customer wants ChatServ to manage both inbound and outbound messaging workflows

Limitations and considerations

• ChatServ becomes the main messaging path.

• Setup may require messaging route changes.

• If the number was previously using ConnectUC messaging, changing the route may affect existing ConnectUC message history.

• Customers should review the impact carefully before changing the primary messaging destination.

Option 2: ConnectUC as Primary, ChatServ as Copy

In this setup, ConnectUC remains the primary messaging destination, and ChatServ receives a copy of inbound messages.

ChatServ can still send messages, but outbound messages sent outside of ChatServ may not be copied back into ChatServ.

This means the ChatServ conversation view may not contain the full conversation history.

Common use cases

• Customer wants to keep using ConnectUC as the main messaging app

• Customer only needs ChatServ for specific outbound messages

• Customer wants to use selected ChatServ advanced features

• Customer wants inbound message copies sent to ChatServ for webhook or automation purposes

Limitations and considerations

• ChatServ may not have the full conversation history.

• Outbound messages sent from ConnectUC may not appear in ChatServ.

• ChatServ automation may not know about replies or communication that happened only in ConnectUC.

• Some advanced ChatServ features may not behave as expected if ChatServ does not have the full message thread.

For example, a drip campaign may send follow-up messages until there is other communication. If the customer replies or communicates in ConnectUC and that outbound activity is not copied to ChatServ, ChatServ may not know the communication happened and may not stop the drip campaign as expected.

The same type of limitation may apply to auto replies or other rules that depend on recent communication history.

Important Note for Existing SkySwitch Messaging Customers

If a SkySwitch customer is already using ConnectUC messaging and later wants to move to ChatServ as the primary messaging destination, the messaging route must be reconfigured.

During this change, ConnectUC messaging may be disconnected from that number.

Existing ConnectUC message history may be lost and may not be recoverable or transferable.

Because of this, customers who already use ConnectUC messaging should review their options carefully before changing ChatServ to the primary destination.

Depending on the use case, the customer may choose one of the following:

• Use ChatServ as the primary messaging destination and accept that existing ConnectUC message history may be lost.

• Keep ConnectUC as the primary messaging destination and use ChatServ as a copy/secondary platform.

• Use ChatServ only for API sending, webhook handling, or selected advanced features where full conversation history in ChatServ is not required.

Teklink cannot guarantee that existing ConnectUC message history can be retained, migrated, or recovered after messaging routes are changed.

Kazoo Customers and ChatServ

For Kazoo customers, Teklink provides SMS/MMS through ChatServ.

ChatServ provides the customer-facing UI and backend for sending and receiving SMS/MMS messages and can also support webhook and API-based messaging integrations as described above.

Kazoo customers who need SMS/MMS integration options should review the ChatServ sections of this article and contact Teklink support for availability, pricing, SMS/MMS enablement, API access, webhook options, and setup requirements.

Customer Responsibility for Messaging Integrations

For any custom SMS/MMS integration, the customer should be prepared to provide or arrange the following:

• A developer or integration partner

• A receiving webhook endpoint, if using webhooks

• API access to their CRM, ticketing system, or custom application

• Secure storage of API keys

• Opt-in and opt-out handling

• Message content review

• Recipient consent tracking

• Compliance review

• Error handling and monitoring

• Testing before production use

• Ongoing maintenance

Teklink can help explain available platform options and provide access where applicable, but customer-owned messaging workflows, external systems, API integrations, webhook processors, automation logic, and compliance handling remain the customer’s responsibility.

Teklink does not normally build, host, support, troubleshoot, or maintain custom customer messaging integrations, webhook processors, middleware, browser extensions, or external applications.

Summary

SMS/MMS integration options depend on the customer’s phone platform, messaging platform, desired workflow, and compliance requirements.

ChatServ can provide a standalone messaging UI, webhook options, outbound SMS API access, and advanced messaging features.

SkySwitch customers may use ConnectUC for basic messaging, SkySwitch inbound webhooks for inbound message notifications, or ChatServ when API access or advanced messaging features are needed.

Kazoo customers use ChatServ for SMS/MMS messaging options.

Customers should contact Teklink support to review current availability, pricing, setup requirements, API access, and webhook options.