SimpleTexting to Slack and HubSpot inbound SMS triage

Build me an agent workflow that triages every inbound text message my SimpleTexting number receives. A human still sends the final reply, the agent only researches, classifies, logs, and drafts.

Trigger: a webhook fired by SimpleTexting whenever a new incoming message arrives. SimpleTexting posts the inbound payload to a webhook URL I configure via its API and Webhooks settings, so this workflow should expose an incoming webhook that SimpleTexting can call. The payload includes the sender phone number, the message body, and the SimpleTexting contact info.

For each inbound message the agent should:

1. Look up the sender's phone number in HubSpot using HubSpot Get Contact (search by phone). If no contact is found, call HubSpot Create Contact to create one using the phone number and any name fields SimpleTexting passes through, so every conversation is tied to a CRM record.

2. Classify the message into exactly one of: sales lead, support question, opt-out or complaint, FAQ, or spam. Use the message body plus any HubSpot context (lifecycle stage, recent notes, deal history) to make the call.

3. Draft a short suggested reply, two to four sentences max, written in a friendly professional tone. If the classification is opt-out or spam, the draft should acknowledge the opt-out or recommend no response. Do not send this reply anywhere. It is for a human to copy.

4. Log the inbound text on the HubSpot contact using HubSpot Create Note. The note should contain the full message body, the classification, and the drafted reply, and it should be associated with the contact record from step 1.

5. Post a structured alert to a Slack triage channel using Slack Send a Message. The Slack message must include: sender name (or phone if name is unknown), classification with an emoji prefix that matches the category, the full inbound message body in a quote block, a clickable link to the HubSpot contact record, and the drafted reply in a code or quote block so it is easy to copy. End the message with a short instruction that whoever takes it should send the reply from SimpleTexting if they approve.

Do not auto-reply via SimpleTexting Send Message. The Send Message operation exists for the human teammate to use manually from the SimpleTexting UI. The agent must stay read-only on the outbound SMS side.

Inputs to expose as workflow configuration: the Slack channel ID for triage alerts, an optional HubSpot owner ID to assign newly created contacts to, and an optional map from classification to Slack channel for teams that want sales leads, support, and complaints routed to different channels.

Additional information

What does this prompt do?

Listens for every inbound SMS that hits your SimpleTexting number and reacts in real time.
Finds the sender in HubSpot by phone number and creates a fresh contact if no record exists yet.
Classifies the message as a sales lead, support question, opt-out or complaint, FAQ, or spam, and drafts a short reply your team can copy and send.
Logs the inbound text and the classification as a note on the HubSpot contact, then posts a triage card to Slack with sender, body, link to the contact, and the draft reply.

What do I need to use this?

A SimpleTexting account with API access enabled so inbound texts can be forwarded to the workflow.
A HubSpot login with permission to read and create contacts and add notes.
A Slack workspace and a triage channel where the alerts should land.

How can I customize it?

Change the Slack channel that receives the triage alerts, or split alerts into different channels per classification.
Tune the categories and the draft reply style so they match how your team actually labels and responds.
Decide what extra context to attach to the HubSpot contact, like adding the sender to a specific list or setting a lifecycle stage on first contact.

Frequently asked questions

Does this reply to the customer automatically?

No. The agent only drafts a suggested reply and posts it to Slack. A teammate has to read it and send the response from SimpleTexting if they approve, so a human always stays in the loop.

What happens if the sender is not in HubSpot yet?

The agent creates a new HubSpot contact using the sender's phone number, then attaches the inbound message as a note. That way every conversation is tied to a CRM record from the very first text.

Which categories does the agent use to classify messages?

Out of the box it sorts each text into one of five buckets: sales lead, support question, opt-out or complaint, FAQ, or spam. You can rename or add categories to fit how your team triages.

Can I send the alert to more than one Slack channel?

Yes. You can route by classification, for example sending sales leads to your revenue channel and support questions to your support channel, or fan out the same alert to multiple channels.

Will this work for MMS or only plain text messages?

It triggers on every inbound message SimpleTexting forwards, including picture messages. The classification and draft reply focus on the text body, and the Slack alert includes the full message content for context.