List the services behind customer messages

Imagine a Michigan manufacturer whose office sends ordinary email through Microsoft 365, order acknowledgements through business software, and newsletters through a marketing platform. A customer sees the company's name on all three. The business needs a record of which services send those messages, who manages each service, and how its use of the company's email domain was approved.

Start with communications that move work forward: quotes, appointment confirmations, invoice notices, support updates, and website acknowledgements. Ask sales, operations, accounting, and marketing to identify the applications they actually use. A professional-services firm may have a proposal tool that only one employee remembers setting up. Give that service a place on the list alongside the main email platform.

Record the addresses and responsible people

For each service, record its business purpose, application name, visible sender address, and intended reply destination. Include any separate sending subdomain. Ask an authorized employee to provide a harmless sample message so IT can inspect the actual sending details. Collect the provider's current domain-verification instructions through its known administration or support route.

Name a business owner who can approve the service's use and an administrator who can manage its settings. Record the provider's support contact and who administers the domain's DNS records. Keep account credentials and private signing material within approved secure systems. The shared review record should identify the people and configuration evidence needed for a decision.

Have IT map authentication to each service

Microsoft describes SPF as a DNS-based check of authorized sources for a message's envelope-sender domain. DKIM adds a digital signature associated with a signing domain. DMARC checks alignment with the visible From domain using SPF or DKIM results. Ask IT to explain which identities each service actually uses and how its messages meet the approved authentication arrangement.

Microsoft's SPF guidance allows only one SPF record per domain or subdomain and describes DNS-lookup limits. Have IT review the complete existing record before implementing a provider's request. Microsoft's DKIM instructions also require retrieving the actual configuration values for the relevant Microsoft 365 domain. Use the current requirements for each provider and account rather than copying example DNS values into production.

Test the business message and its reply

Choose a representative message from each important service and agree on approved test recipients. Use fictional customer details and a clearly labeled sample wherever the application permits. In the manufacturer example, test the order acknowledgement from the business application itself. Give IT the sending time, service used, destination, and resulting message for the technical check.

Have the receiving person confirm the sender shown, readable content, expected links or attachments, and where a reply arrives. Check that the responsible team can find and handle that reply. Ask IT to review authentication results and investigate any delivery error. Record the complete business outcome along with the technical result so a passing check corresponds to a usable customer communication.

Plan authentication changes with monitoring

Microsoft recommends a gradual DMARC rollout with testing and monitoring to avoid unintentional failures affecting legitimate mail. Have IT propose the appropriate change plan for the business's current settings and sending services. Agree on the services to verify, the people approving the change, and how unexpected delivery problems will be reported and handled.

Assign review of the available authentication reports to someone who understands the sending inventory. Ask IT to compare observed sources and failures with the approved services and investigate unfamiliar entries. Include occasional communications, such as a monthly statement or seasonal campaign, in the verification schedule. Keep authentication review connected to ordinary message-security practices and recipient feedback.

Close out services that stop sending

When replacing a proposal, accounting, or marketing tool, identify the messages that must move to the successor. Verify the new workflow before the business owner authorizes retirement of the old sending arrangement. Have IT review the related domain configuration and remove obsolete authorization through the approved change process, accounting for any dependencies that still need it.

Update the inventory with the replacement owner, verification result, and retirement decision. Review the list when a department adds an application, changes providers, or loses its original administrator. A useful closeout leaves the business able to explain how its next quote, confirmation, or account notice will be sent and who will resolve a problem with it.

Bring this record to your next IT review

Choose one business application that sends customer messages and document these details with its owner.

  • Service name, business purpose, and responsible administrator.
  • Sender address, sending subdomain, and intended reply destination.
  • Provider requirements and IT's verified authentication arrangement.
  • Sample-message result, reply handling, and unresolved delivery issues.
  • Monitoring owner and coverage for occasional message types.
  • Replacement or retirement plans and the next review date.

YOUR NEXT STEP

Build a sending-service inventory around the messages your business relies on. Give each service an owner, have IT verify its domain authentication, and confirm that the recipient can use and reply to the actual message.

Need a hand putting a plan in place? Explore our Managed IT services for Michigan businesses or talk with our team.

Further reading