Dynamics 365 Customer Service Visitor Management, Case Management & Teams Telephony

Microsoft Dynamics 365 Customer Service + Microsoft Teams Telephony

Modern customer service organizations often manage walk-in visitors, phone calls, website requests, documents, queues, and case follow-ups across multiple systems. This can make it difficult for service agents to understand who owns a case, what stage it is currently in, what documents are pending, and what action needs to happen next.

Microsoft Dynamics 365 Customer Service can provide a centralized case management platform while Microsoft Teams Phone can provide integrated business telephony. Together, they can create a unified workspace where agents can manage customer information, cases, queues, activities, and phone interactions from a connected environment.

1. Business Scenario

Consider a community service organization that receives requests through multiple channels such as walk-in visitors, telephone calls, website forms, and digital messaging.

The organization wants service agents to have a single view of the customer and their cases. Reception staff should be able to quickly check in visitors, issue queue tokens, and route visitors to the appropriate service team.

When a customer calls, the agent should be able to identify the caller, see open cases, understand the current case owner and stage, and answer the customer's question without searching multiple systems.

2. Solution Objectives

• Create a centralized customer and case management platform.
• Provide reception-driven walk-in check-in.
• Generate queue tokens automatically.
• Route visitors and cases to the appropriate service queues.
• Provide a lobby display showing waiting and currently served visitors.
• Provide a structured six-stage case lifecycle.
• Provide category-specific document checklists.
• Integrate Microsoft Teams Phone with Dynamics 365.
• Provide inbound caller identification and screen-pop.
• Provide click-to-dial from customer and case records.
• Allow phone calls to be converted into new cases.
• Allow website requests to create cases.
• Provide automated customer notifications.
• Provide SLA tracking.
• Provide supervisor dashboards and Power BI reporting.

3. Prerequisites

Before starting the implementation, the following platform, environment, administration, and licensing prerequisites should be confirmed.

3.1 Microsoft Platform Prerequisites

• Microsoft Dynamics 365 Customer Service environment.
• Microsoft Dataverse environment.
• Power Apps access.
• Power Automate access.
• Microsoft Teams tenant.
• Microsoft Teams Phone capability for phone-handling users.
• Microsoft Teams administration access.
• Appropriate security roles for receptionists, caseworkers, supervisors and administrators.
• SharePoint Online if document management is required.
• Power BI if management and reporting dashboards are required.

3.2 Telephony Prerequisites

The demonstration environment should have Microsoft Teams Phone with a Calling Plan and a test telephone number provisioned for phone-handling users.

As an alternative, a Direct Routing test number can be used where the telephony architecture requires an external carrier or existing telephony infrastructure.

3.3 Direct Routing Alternative

A Direct Routing implementation normally requires Microsoft Teams Phone, a supported Session Border Controller or telephony provider architecture, SIP connectivity, a telephone number, and appropriate Teams administration and configuration.

For a PoC, the exact Direct Routing architecture should be confirmed with the organization's telephony provider before implementation.

4. Licenses and Commercial Prerequisites

The final licensing design depends on the number and type of users, enabled channels, telephony architecture, and reporting requirements.

5. High-Level Solution Architecture

                    Customer / Visitor
                           |
          -------------------------------------
          |                 |                 |
       Walk-In            Phone            Website
          |                 |                 |
          v                 v                 v
    Reception          Teams Phone        Power Pages
          |                 |                 |
          v                 v                 v
       Visit           Caller Match        Case
          |                 |                 |
          ----------- Dynamics 365 ----------
                         |
                         v
                    Dataverse
                         |
        --------------------------------
        |              |               |
       Case          Queue            Contact
        |              |               |
        v              v               v
      BPF         Token Logic      Customer History
        |
        v
Document Checklist
        |
        v
Notifications
        |
        v
Supervisor Dashboard
        |
        v
      Power BI

6. D365 Data Model

The solution uses Dataverse tables to maintain customer, visit, case, queue, service category, document checklist and activity information.

7. Service Category Management

The solution should maintain a master list of service categories. The service category selected during intake should drive case classification, routing, reporting and, where applicable, SLA behavior.

The PoC should support the defined service-category master list together with an OTHERS catch-all category for requests that do not currently fit an existing category.

The category master should be maintained centrally so that new categories can be introduced without redesigning the entire case-management solution.

8. Reception-Driven Walk-In Check-In

The walk-in process begins at the reception desk. The receptionist searches for the customer using available identifying information.

Customer Arrives
      ↓
Search Contact
      ↓
Existing Contact?
   /          \
 Yes           No
  |             |
  |        Quick Create
  |             |
  -------> Contact
             |
             v
      Select Service Category
             |
             v
          Check In
             |
       ---------------
       |             |
       v             v
     Visit         Case
       |
       v
   Queue Token

9. Queue and Token Management

After check-in, the system generates a queue token and routes the visitor to the appropriate service queue.

Check In
   ↓
Service Category
   ↓
Category Group
   ↓
Service Queue
   ↓
Daily Sequence
   ↓
Queue Token

A token can use a simple format such as:

Power Automate can be used to manage daily sequencing and queue-routing logic.

10. Lobby Display Canvas App

A Canvas App can be used as a visitor-facing lobby display. The application can run in a browser on a wall-mounted monitor or TV.

NOW SERVING

WAITING

The display should automatically refresh so that visitors can see when their token is called.

11. Caseworker "Next Visitor"

Caseworker Queue
       ↓
Next Visitor
       ↓
Oldest Waiting Token
       ↓
Set Status = Now Serving
       ↓
Update Lobby Display
       ↓
Open Related Case
       ↓
Open Customer History

The caseworker should be able to select the next waiting visitor from their service queue. The corresponding case should open with the customer's history available.

12. Six-Stage Case Lifecycle

The Case lifecycle is implemented using a Business Process Flow so that staff can immediately understand where a case is in the process.

1. Intake
      ↓
2. In Review
      ↓
3. Docs Pending
      ↓
4. Submitted to Agency
      ↓
5. Decision
      ↓
6. Resolved / Closed

12.1 Intake

The customer is identified, the service category is selected and the Case is created. The originating channel is captured.

12.2 In Review

The caseworker reviews the request, performs initial eligibility checks and initiates the appropriate document checklist.

12.3 Docs Pending

Required documents are collected and attached to the Case. Automated reminders can be triggered when documents remain outstanding.

12.4 Submitted to Agency

The application or request is submitted to the appropriate external agency. A confirmation or reference number can be recorded against the Case.

12.5 Decision

The agency outcome is recorded as appropriate.

12.6 Resolved / Closed

Once the outcome has been communicated and all required actions have been completed, the Case can be resolved and closed.

13. Case Status at a Glance

The Case form should provide an easy-to-understand view of:

• Case owner.
• Current Case status.
• Current BPF stage.
• Service category.
• Originating channel.
• Time spent in the current stage.
• Last activity.
• Required documents.
• Related customer history.

14. Case Ownership and Reassignment

Cases should have clear ownership so supervisors can understand who is responsible for the next action.

Case Owner
    ↓
Caseworker
    ↓
Work Completed
    ↓
Reassignment Required?
    ↓
New Owner
    ↓
Audit / Timeline

Ownership changes should remain traceable through the Case timeline and audit capabilities.

15. Category-Specific Document Checklist

Different service categories may require different documents. The solution should generate a checklist based on the selected category.

Service Category
       ↓
Checklist Template
       ↓
Required Documents
       ↓
Document Received?
    /          \
  Yes           No
   |             |
Complete       Pending
   |             |
   -------> Docs Pending

For the PoC, representative service categories can be selected to demonstrate different checklist complexity, such as a document-heavy service, a benefits-related service, and a simple service.

Documents can be attached to the Case and optionally managed through SharePoint integration.

16. Microsoft Teams Phone Integration

Microsoft Teams Phone can provide the telephony layer while Dynamics 365 Customer Service provides the customer and Case context.

Microsoft Teams Phone
        |
        v
Business Telephone Number
        |
        v
Incoming Customer Call
        |
        v
Caller Identification
        |
        v
Dynamics 365 Customer Service
        |
        v
Contact + Open Cases

16.1 Calling Plan

For a straightforward PoC, Microsoft Teams Phone with a Calling Plan and a test telephone number is the recommended approach.

The exact Calling Plan availability, geographic support, number assignment and commercial pricing should be validated for the deployment country and tenant.

16.2 Direct Routing Alternative

Direct Routing can be used when an organization needs to connect Teams Phone to an external carrier or existing telephony infrastructure.

Microsoft Teams Phone
        ↓
Direct Routing
        ↓
SBC / Telephony Provider
        ↓
PSTN
        ↓
Customer

The exact Direct Routing architecture depends on the selected carrier, SBC model, network design and telephony requirements.

17. Inbound Call Screen-Pop

Incoming Call
      ↓
Identify Caller
      ↓
Match Contact
      ↓
Find Open Cases
      ↓
Open Customer Context
      ↓
Agent Answers

When a known customer calls, the agent should be able to quickly access the matching Contact and open Case information.

18. Click-to-Dial

Agents can initiate calls from supported Contact or Case records using the integrated Teams telephony experience.

Contact / Case
      ↓
Telephone Number
      ↓
Click-to-Dial
      ↓
Teams Phone
      ↓
Customer Call

19. Convert Phone Call to Case

When a customer calls about a new service request, the agent should be able to create a Case from the phone interaction and reuse the caller's Contact information.

Incoming Call
      ↓
Identify Contact
      ↓
Create / Convert to Case
      ↓
Caller Information Pre-Populated
      ↓
Select Service Category
      ↓
Route Case

20. Call Activity and Timeline

Phone interactions should be represented in the Dynamics 365 activity timeline so that agents and supervisors can understand the communication history related to the Case.

Teams Call
    ↓
Phone Activity
    ↓
Case Timeline
    ↓
Agent Notes / Follow-Up

21. Website Request to Case

A website request form can capture customer information and the selected service category. The request can then create a Dataverse Case automatically.

Website Form
     ↓
Customer Information
     ↓
Service Category
     ↓
Dataverse
     ↓
Create Case
     ↓
Queue Routing

Power Pages or another supported customer-facing form experience can be used for this scenario.

22. Social and Digital Messaging

Digital messaging channels such as supported social or messaging platforms can be integrated through the appropriate Dynamics 365 digital messaging capabilities.

Digital Message
      ↓
Digital Messaging
      ↓
Customer Identification
      ↓
Case Creation
      ↓
Queue / Agent

23. Repeat Customer Recognition

A returning customer should not need to provide the same information repeatedly. The Contact record becomes the central customer identity across visits, phone calls and Cases.

Phone / Name Search
        ↓
Existing Contact
        ↓
Reuse Contact
        ↓
New Visit / Case
        ↓
Existing History

Duplicate detection and data-quality controls should be configured to reduce duplicate Contact records.

24. Automated Customer Notifications

Case Created
     ↓
Notification

Status Changed
     ↓
Notification

Documents Pending
     ↓
Reminder

Case Resolved
     ↓
Completion Notification

Power Automate can orchestrate email notifications and, where required and appropriately licensed/configured, SMS notifications.

25. SLA Management

Different Case priorities may require different response or resolution expectations. Dynamics 365 Customer Service SLA capabilities can be used to track these targets.

Case Priority
     ↓
SLA Policy
     ↓
SLA KPI
     ↓
Timer
     ↓
Warning / Breach

26. Power Automate Automation

Power Automate can connect different components of the solution and automate repetitive tasks.

• Queue token generation.
• Queue routing.
• Customer notifications.
• Document reminders.
• Case status notifications.
• Case resolution notifications.
• Website request processing.
• Integration with approved external services where required.

27. Power Apps Components

Power Apps can extend the standard Dynamics 365 experience where a specialized user interface is required.

28. Supervisor Dashboard

Supervisors require a consolidated view of operational performance.

29. Power BI Reporting

Power BI can provide management and program-level reporting using Dataverse data.

Dataverse
    ↓
Cases / Visits / Categories
    ↓
Power BI Dataset
    ↓
Management Dashboard
    ↓
Program / Funder Reporting

• Clients served by program.
• Cases by service category.
• Cases by lifecycle stage.
• Case aging.
• Queue performance.
• Workload by caseworker.
• Monthly service volume.

30. Security and Access Control

Access should be controlled using Microsoft security roles, Dataverse permissions, business units, teams and other appropriate security mechanisms.

31. Multi-Language Considerations

Where multiple languages are required, the solution should consider language support for reception interactions, customer notifications and the lobby display.

Customer Language
       ↓
Reception Experience
       +
Notification Template
       +
Lobby Display

The exact languages and translation requirements should be confirmed during discovery.

32. Complete End-to-End Process

Customer
   ↓
Walk-In / Phone / Website / Digital
   ↓
Identify Contact
   ↓
Create Visit / Case
   ↓
Select Service Category
   ↓
Queue Routing
   ↓
Token
   ↓
Caseworker
   ↓
Intake
   ↓
In Review
   ↓
Docs Pending
   ↓
Submitted to Agency
   ↓
Decision
   ↓
More Information?
   |
   +---- Yes ----> Docs Pending
   |
   +---- No
          ↓
   Resolved / Closed
          ↓
   Customer Notification
          ↓
   Reporting

33. PoC Demonstration Flow

34. PoC Demo Data

The demonstration environment should use synthetic or sample data only. No real customer or confidential production information should be used in the PoC environment.

• Sample customer/contact records.
• Sample cases.
• Multiple service categories.
• Cases in different lifecycle stages.
• Sample caseworker users.
• Sample receptionist user.
• Sample supervisor user.
• Sample service queues.
• Sample documents for checklist demonstrations.

35. Out of Scope / Future Roadmap

• Self-service visitor kiosk.
• Behavioral health clinical records.
• Clinical scheduling and HIPAA-specific functionality.
• Volunteer and donor management.
• Production data migration.
• Live external agency system integrations.
• Full live social-channel implementation.
• Advanced D365 Contact Center Voice implementation.
• Automatic call recording and advanced transcription as a core PoC feature.

36. Future Telephony Roadmap

The initial PoC can use Teams Phone integrated with Dynamics 365. Organizations that later require advanced contact-center functionality can evaluate a broader voice architecture.

PoC
Teams Phone + Dynamics 365
        ↓
Future Evaluation
D365 Contact Center Voice
        ↓
Advanced Voice Capabilities
        ↓
IVR / Skills / Transcription /
Sentiment / Supervisor Monitoring

37. Recommended PoC Environment

A dedicated demonstration environment should be used to prevent accidental exposure of production data and to allow configuration changes without affecting business operations.

• Dynamics 365 Customer Service environment.
• Dataverse database.
• Power Apps.
• Power Automate.
• Microsoft Teams.
• Teams Phone test number.
• SharePoint document library.
• Power BI workspace/report.

38. Implementation Approach

Phase 1
Environment Setup
        ↓
Phase 2
Dataverse & D365 Configuration
        ↓
Phase 3
Case Lifecycle & BPF
        ↓
Phase 4
Queue & Token Management
        ↓
Phase 5
Canvas Lobby Display
        ↓
Phase 6
Teams Phone Integration
        ↓
Phase 7
Power Automate
        ↓
Phase 8
Dashboard & Power BI
        ↓
Phase 9
Testing
        ↓
Phase 10
Demo Rehearsal

39. Testing Scenarios

40. PoC Success Criteria

• A walk-in customer can be checked in, queued, served and case-managed without paper.
• A phone status inquiry can be answered quickly using customer and Case information.
• The Case lifecycle can be demonstrated from Intake through Resolution.
• Category-specific document requirements can be demonstrated.
• Queue and token management works correctly.
• Teams Phone integration demonstrates caller context and click-to-dial.
• Supervisors can view workload and Case performance.
• Power BI reporting provides useful management information.
• The solution demonstrates a scalable foundation for future channels and capabilities.

41. Key Takeaways

• Dynamics 365 Customer Service provides centralized Case and customer management.
• Dataverse provides the underlying data platform.
• Reception-driven check-in provides a controlled walk-in experience.
• Queue and token management improves visitor flow.
• A Canvas App can provide a simple lobby display.
• A Business Process Flow provides structured Case lifecycle management.
• Category-specific checklists improve document tracking.
• Teams Phone provides integrated business telephony.
• Calling Plan is a straightforward telephony option for a PoC.
• Direct Routing can be used as an alternative telephony architecture.
• Inbound calls can provide customer and Case context.
• Click-to-dial improves agent productivity.
• Phone interactions can be converted into Cases.
• Power Pages can support website-based Case creation.
• Power Automate can automate notifications and business processes.
• Power BI can provide operational and management reporting.
• SLA capabilities can help monitor Case response and resolution targets.
• Future capabilities can be added without redesigning the complete platform.

42. Final Solution Flow

                   CUSTOMER
                      |
       --------------------------------
       |              |               |
     WALK-IN         PHONE          WEBSITE
       |              |               |
       v              v               v
  RECEPTION      TEAMS PHONE     POWER PAGES
       |              |               |
       |         SCREEN POP            |
       |              |               |
       -------> CONTACT <--------------
                  |
                  v
              VISIT / CASE
                  |
                  v
          SERVICE CATEGORY
                  |
                  v
             QUEUE ROUTING
                  |
                  v
              TOKEN
                  |
                  v
           CASEWORKER
                  |
                  v
              INTAKE
                  |
                  v
             IN REVIEW
                  |
                  v
            DOCS PENDING
                  |
                  v
        SUBMITTED TO AGENCY
                  |
                  v
              DECISION
              /      \
     MORE INFO        COMPLETE
        |                |
        v                v
 DOCS PENDING       RESOLVED
                         |
                         v
                  NOTIFICATION
                         |
                         v
                 DASHBOARD / BI

43. Conclusion

Microsoft Dynamics 365 Customer Service combined with Microsoft Teams Phone, Power Apps, Power Automate, SharePoint and Power BI can provide a centralized platform for managing customer service operations.

The solution connects reception intake, visitor queues, Case management, document collection, phone interactions, notifications and management reporting into a single service-management experience.

The recommended PoC approach starts with Dynamics 365 Customer Service and Teams Phone using a Calling Plan, while Direct Routing and advanced Contact Center capabilities can be considered when the telephony architecture or future business requirements justify them.