E-commerce
July 1, 2026
Not all customers want to be contacted in the same way. Some prefer email for confirmations, SMS for delivery, WhatsApp for support, and no marketing messages at all.
The chatbot can help manage these preferences, but it must respect consent and distinguish transactional messages from marketing communications. Poor management can cause annoyance or compliance issues.
This guide explains how to use an AI chatbot to understand, modify, and respect customer communication preferences.
Summary
Why do communication preferences matter?
A useful message on the wrong channel can become a nuisance. An unwanted marketing SMS, a lost follow-up email, or an unexpected WhatsApp notification can degrade the relationship.
The customer must be able to choose how they receive important information. The chatbot can make this choice simple, especially when the customer doesn't know where to change their preferences.
Good communication is not just the right message. It is also the right channel, at the right time, with the right consent.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What types of messages should be distinguished?
The bot must distinguish transactional messages, such as order confirmation, delivery tracking, or refund, from marketing messages, such as promotions, new arrivals, or recommendations.
This distinction is important because consent rules and customer expectations are not the same. A customer may refuse marketing promotions while wanting to receive delivery alerts.
How to request the preferred channel?
The bot can simply ask: "For updates on this order, would you prefer to receive information by email, SMS, or WhatsApp if available?"
The question must specify the type of message involved. Otherwise, the customer might believe they are consenting to all communications from the brand.
How do I manage unsubscribing?
If the customer wishes to stop receiving messages, the chatbot must assist them without making them feel guilty. It must explain what will be stopped and what may remain necessary for order tracking.
For example: "I can help you stop marketing messages. You will continue to receive essential information related to your orders."
What should I do if the customer does not receive the messages?
The bot must verify the email address, the number, the chosen channel, preferences, spam, sending status, and any consent blocks.
It must also propose an alternative channel if an important message does not go through, notably for delivery or order confirmation.
This verification is important because a missed message can have a concrete impact: uncollected package, misunderstood refund, or missing order confirmation.
Which flow to follow?
The flow must respect the customer's choice.
Identify the request: choose a channel, modify, unsubscribe, or report a missing message.
Distinguish between transactional and marketing communication.
Verify consent and the relevant contact details.
Confirm the change in plain language.
Escalate if the preference is not saved or if the customer reports abuse.
Which messages should be used?
To choose a channel: "For order updates, you can choose the most convenient channel from the available options."
For marketing: "I can unsubscribe you from promotional communications. Messages necessary for order tracking can still be sent."
For a missing message: "Let's first check the registered channel and the address used for your order."
When to transfer?
Transfer is necessary if the customer reports unsolicited messages, an inability to unsubscribe, a sensitive number error, or a preference that is not updating.
The bot must transmit the account, the channel concerned, the type of message, the requested preference, and the example of the message received if available.
Which KPIs should be monitored?
Track preference changes, unsubscribes, bounces, complaints by channel, and missed transactional notifications.
These metrics show whether the brand is communicating too much, not enough, or on the wrong channels.
Which mistakes should be avoided?
Avoid mixing marketing consent with order tracking, making unsubscription difficult, or changing a channel without clear confirmation.
The customer must feel that they remain in control. This is the foundation of a relationship of trust.
How can Qstomy help?
Qstomy can help customers understand and modify their communication preferences, while respecting consent rules and message types.
The chatbot simplifies channel management without confusing service, marketing, and essential notifications.
Explore AI support or request a demo.
PREF-FLOW bot checklist (12 steps)
Audit pref/unsubscribe/spam tickets 90 days per channel
Map 14 intents pref_* section 3
Document consent snapshot per channel (Klaviyo, SMS, WhatsApp)
Configure PF-1 to PF-8 flow bot + quick replies
Connect sync APIs orchestrator + idempotence
Enable audit log PF-6 (timestamp, source, wording)
Publish multi-channel preference center /preferences
Define 7 handoff triggers + ticket brief
Train agents 45 min (audit log, complete sync fail)
Staging profile tests per channel pref_mixed_custom
Weekly pref_bot KPI dashboard #support + #marketing
Quarterly legal review + win-back exclusion flows
In short
#382 = multi-channel bot, #381 = customer service email agents
PREF-FLOW: 8 steps identify → preference center
Granular consent: separate email, SMS, WhatsApp
Audit PF-6: mandatory 2026 compliance
KPI pref_bot_resolution: target > 55%
FAQ
Difference with #381 newsletter unsubscription?
#381 = email UNSUB-FLOW agents process. #382 = preferences bot automation email + SMS + WhatsApp + notifications.
Can the bot activate SMS marketing?
Yes via pref_opt_in_new with explicit double opt-in. Never silent activation.
Customer wants to stop order confirmations?
Bot explains legal transactional emails/SMS. Handoff #383 if data deletion request.
STOP SMS received outside chat?
SMS provider honors immediately. Bot sync PF-6 if bidirectional integration. Audit same rules.
Delay to stop promos after bot?
24-72 hours propagation for queued campaigns. Bot systematically mentions PF-7.
Go further
Test PREF-FLOW this week: simulate pref_mixed_custom (email off, SMS delivery on) on staging profile, check Klaviyo + Attentive sync + audit log in less than 5 min.
Share this guide #382 with support, marketing, and DPO: a well-configured preferences bot transforms multi-channel consent into a trust, measurable, and compliant benefit.
Enzo
July 1, 2026
