Choose the job you need SMS to do
You can use GoDesk for SMS without buying a PBX or contact centre. Choose a campaign interface for your team, an API connection for your application, or both.
A campaign sends planned content to a selected audience. A transactional message follows an event, such as an order update. An API lets an application request the message; your application remains responsible for the event and business logic. Agree the supported connection and sending process with GoDesk.
Prepare the first setup
- Your business details and desired sender name or two-way reply route.
- The recipient countries and networks you need to reach.
- An authorised contact list and the purpose of each message.
- The quantity of SMS you want to order.
- Your application and developer contact, if you need API connectivity.
- Who will handle replies or customer calls after a campaign.
GoDesk helps scope sender approvals, access and integration requirements. Read the sender ID and reply route guide before choosing the sender.
Test before sending to the audience
Use authorised test contacts to check the sender, wording, links and any personalisation. Review the message-part count and expected cost. If two-way messaging is configured, test the reply route and team assignment as well.
For an API connection, have your developer test the agreed request and result handling. Keep credentials in the approved secure setup process. Do not include them in ordinary support messages.
Launch with a plan for the response
Choose the sending time and pace. Make sure the team can handle resulting enquiries. Review sending results, investigate failures and record what you would change before repeating the campaign.
Next: understand costs and message parts. Explore the standalone SMS solution.