SMS orders#

SMS intake captures short orders from field teams, stores, or sales reps. StackCube records the text and attachments in intake history, links the sender phone number to a customer, and creates a pending order candidate in the order list.

How SMS Intake Works#

Basic flow:

1. Enable SMS in Channels.
2. Connect the StackCube webhook URL and header value to an external SMS receiving service.
3. The customer sends an order to the configured receiving number.
4. StackCube normalizes sender number, recipient number, provider, message body, and attachments.
5. If the sender number is unknown, StackCube asks for the customer login ID by SMS.
6. When the customer replies with the ID, StackCube links that phone number to the customer.
7. On the next order, the same phone number is remembered and can create an order candidate without another customer prompt.

SMS intake does not approve orders automatically. Review customer, items, quantities, prices, delivery requests, and duplicate risk before approval.

What StackCube Can Receive#

SMS intake can process:

• Short text orders
• Field orders with only item names and quantities
• Longer LMS message bodies
• MMS images and order sheet photos
• Excel, CSV, and PDF attachments when the SMS provider forwards file content
• Recent order lookup requests

Attachment recognition depends on the SMS provider sending the actual file content through the webhook. If the provider only sends a file name or media URL without content, the trace may be visible in intake history but automatic analysis can be limited. In that case, use the Manual SMS tab in the order list and attach the files directly.

Remembered Phone Numbers#

StackCube normalizes sender phone numbers and stores the link on the customer. Once linked, future messages from that number are matched to the same customer.

Review carefully when:

• One shared phone sends orders for multiple customers.
• A buyer changes phone numbers.
• One customer uses several sender numbers.
• A wrong customer ID linked the phone number to the wrong customer.

If phone matching looks wrong, confirm the customer in intake history and the order list before approval. Keep recurring valid numbers organized in customer records so future messages match automatically.

SMS Webhook Setup#

SMS intake does not read phone messages directly. An external SMS receiving service forwards the source message to StackCube by webhook. In Channels, confirm:

• Webhook URL
• Header name
• Header value
• Query-included URL
• Provider memo
• Receiving number

Providers use different field names, so send a short test message right after connecting. Confirm that the test appears in intake history and that sender and recipient numbers look correct.

See channel settings and intake history for the full setup fields.

Manual Intake for Existing Messages#

For already received SMS/MMS messages or test text, use Manual registration in the order list and choose the Manual SMS tab. Paste the text and attach images, Excel, CSV, or PDF files so the source stays with the candidate in the same review queue.

Good Rollout Pattern#

SMS is fast, but short messages often omit context. Share a simple format first.

Item quantity / delivery request
Coffee beans 5 boxes / Friday morning delivery

During the first week, review phone matching errors, missing receiving numbers, and provider-specific attachment behavior daily. SMS intake is useful for fast capture, but reviewers should still inspect the source before approval.