Carry communication preferences into messaging tools

What this means for your practice

Choose the main record of communication preferences and identify the messages that must follow it. The responsible team sets the rules; the connection should carry those decisions accurately.

Questions to take to your supplier

Change a fictional preference and inspect the next proposed message. Ask which system holds the main preference record and how updates move. Your responsible team decides the applicable communication rules; the supplier demonstrates that the integration follows them.

Agree the working process

Identify the system the organisation trusts for each relevant communication preference and who may change it. Different communication types may follow different approved rules, so the responsible team should define the required behaviour before the supplier connects fields. Write examples in business language: a preference changes, a message is already queued, or a contact record is updated in another tool. Ask the supplier to show the outcome in the actual outgoing process, not just that a field was copied somewhere. Keep failed or delayed updates visible to an owner so the team can follow the approved response.

Decide how staff confirm a correction reached the relevant tools without independently changing several copies and creating another conflict. Include current-state checking before an eligible message in testing. Review exceptions with the people who own the communication rules. The integration should faithfully carry out those decisions, while questions about which rules apply remain with the organisation's responsible advisers and processes rather than a generic connector setting.

How to check the result

Count messages proposed against the current recorded preference.