Landis Attendant Console for Microsoft Teams
  • About
  • Getting Started
  • Daily Usage
    • Layout
    • Notifications
    • Teams Presence
    • Teams Status Message
    • Call Handling
    • Search for Contacts
    • Contacts
    • Contact Groups
    • Call Details
    • Call History
    • Voicemail
    • Contact Card
    • Click to Dial
    • Call as Delegate (Coming Soon!)
  • Settings
    • General
    • Search
    • Contacts
    • Caller Info
    • Transfer
    • Devices
    • Layout
    • Keyboard Shortcuts
    • Quick Access Shortcuts
    • Connectors
    • Permissions
    • AI Prompts
    • Advanced
  • Administration
    • Settings Policies
      • Access Settings Policies
      • Configuring Settings Policies
  • Appendix
    • Advanced Settings
    • App Service Information
    • Attendant Pro Comparison
    • Custom Layout
    • Desktop App Antivirus Exclusions
    • Desktop App / Browser Feature Comparison
    • Desktop App Minimum Requirements
    • Enable Chat Consult Transfer
    • External Search
    • Integration Permissions
    • Known Limitations
    • Network Recommendations
    • Restricting Application Access
    • Supported Audio Devices
    • Supported Browsers
    • USB Audio Device Call Control Buttons (Preview)
    • Feature States
    • Release Notes
  • Knowledge Base
  • Service Health
    • Current Incidents
    • Incident Reports
  • Feature Highlights
    • Chat Callback Reminder
    • Call User Quick Access Shortcut
    • Teams Queues Sign In/Out
    • Dark Mode
    • Hold Alerts
  • What's New in Attendant Console
  • Download the Desktop App
  • What is an Attendant Console for Microsoft Teams
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Appendix

External Search

External search can query your custom search API and the response from the API can return contact information that will be shown in the search panel. A simple execution of this can be created by using Microsoft Flow.

External Search will send a HTTP POST to the specified URL. A JSON object with specific properties is sent in the body. The response body JSON array object(s) are expected to have specific property names.

Example HTTP POST Body:

Only populated properties will be sent in the body.

{
  "searchTerm": "John Doe",
  "departments": [
    "Sales"
  ],
  "officeLocations": [
    "New York"
  ],
  "countries": [
    "USA"
  ],
  "jobTitles": [
    "Sales Manager"
  ],
  "postalCodes": [
    "10002"
  ],
  "givenName": [
    "John"
  ],
  "surname": [
    "Doe"
  ],
  "displayNames": [
    "John Doe"
  ],
  "mail": [
    "jdoe@contoso.com"
  ],
  "userPrincipalName": [
    "jdoe@contoso.com"
  ],
  "maxContactSearchResults": "20"
}

Example HTTP Response Body:

All properties are optional and the values can be null.

Properties are case sensitive.

Properties that are not expected will be ignored.

[
    {
        "azureAdId": null,
        "givenName": "John",
        "surname": "doe",
        "displayName": "John doe",
        "userPricipalName": "jdoe@contoso.com",
        "companyName": "Contoso",
        "jobTitle": "Sales Manager",
        "department": "Sales",
        "officeLocation": "New York",
        "emailAddress": "jdoe@contoso.com",
        "businessPhone": "810-653-3163",
        "mobilePhone": "810-653-3163",
        "preferredLanguage": null,
        "notes": null,
        "country": "USA"
    }
]

Last updated 1 year ago

Was this helpful?