Dynamics 365 Franchise Notifications

I already have Microsoft Dynamics 365 Field Service creating Work Orders and, at the moment a Work Order is created, a Power Automate flow fires off an email and a Twilio SMS/MMS to the customer. The challenge is that the same instance also dispatches for multiple franchisees, each with its own name style, street address, local phone number and logo. I want the flow to look at the customer’s assigned Business Unit or Territory and automatically merge the correct franchise data into every message.

See attached Franchise-Aware Customer Email, SMS and
MMS.pdf for details and instructions but not limited.

What the message must hold every time it goes out:
• Customer details
• Franchisee details (name style, address, local phone number)
• Work Order details
• The franchisee logo embedded as an SVG
• Any extra fields described in the attached Developer Implementation Specifications

Scope of the work
1. Extend or rebuild the existing “When a Work Order is Created” trigger flow so it fetches the related Business Unit or Territory, pulls the matching franchise record and injects the right variables into both the email body and the Twilio SMS/MMS payload.
2. Create or update reusable HTML/JSON templates so the message layout is clean and the SVG logo renders correctly across common mail clients and phones.
3. Add environment-safe variables or a configuration table in Dataverse so new franchisees can be added without editing the flow again.
4. Document every step clearly so I (or another admin) can maintain it later, including screenshots of key settings, expression formulas and the Twilio connector configuration.

Acceptance criteria
• A single test Work Order for Franchisee A sends an email and SMS that display the correct address, local phone and SVG logo for Franchisee A.
• Repeating the test for Franchisee B swaps in Franchisee B’s branding with no manual edits to the flow.
• The flow runs only on create; updates to the Work Order do not retrigger it unless we explicitly switch that on later.
• All configuration is stored centrally so adding a franchisee requires data entry only, not flow edits.

If you have solid experience with Dynamics 365 Field Service, Dataverse tables and the Twilio connector inside Power Automate, this should be a straightforward build. Let me know how you would structure the configuration table and any best-practice tips you plan to apply.