Request a DemoCommunication channel
iService Email to SMS lets agents send appointment reminders and status updates from the customer conversation. Sinch MessageMedia delivers each text. Customer replies return to the agent who sent the message, and iService stores the SMS with the email conversation in interaction history.
Appointment reminders and status updates may need attention sooner than customers read email.
iService lets agents send those updates by SMS from the customer conversation. Sinch MessageMedia handles delivery to the customer. When the customer replies, iService sends the response to the original agent and records the exchange in interaction history.
Service teams use Email to SMS when a customer needs a timely update.
Your agents can text an appointment reminder or a status change from the iService conversation. The customer receives the update by SMS and can reply to the agent who sent it. The messages remain attached to the customer interaction.
An E2S login turns the customer mobile number into an address for SMS delivery.
iService stores the texting address as an E2S login on the customer contact. This login type is separate from the regular email login and is structured for delivery through Sinch MessageMedia. An agent sends the text from the iService conversation. Sinch MessageMedia delivers it, and iService routes the reply to the original sending agent. The outgoing text and reply remain in interaction history.
A customer records consent before an agent sends an appointment update by text.
A customer completes an iService submit form and selects SMS Opt-In. The form records consent on the contact and creates an E2S login from the customer mobile number. Later, an agent sends an appointment update from the customer conversation. Sinch MessageMedia delivers the text. The customer replies, and iService routes that response to the same agent. The update and reply stay in the interaction history with the customer email.
Agents can review the complete customer conversation in iService across both channels.
iService stores each outgoing text and customer reply beside the email conversation in interaction history. Agents can review the update, the response, and the earlier email exchange from the same customer conversation. The service record shows what the agent sent and how the customer answered.
SMS Opt-In records the customer consent used to create the texting address.
iService records SMS Opt-In on the contact before texting begins. Selecting the opt-in on an iService submit form creates the E2S login for that customer. Your team can check the consent on the customer record and confirm the mobile number linked to the texting address.
Request a demo to see SMS Opt-In create an E2S login, an agent send a customer update, and the reply return to the same conversation.