Skip to main content

Webex App - Post-Call Emergency Alerts

Overview​

The Webex Teams app posts messages to Webex Teams spaces when specific call events occur. Use this app to notify teams about emergency calls, security incidents, or any events requiring immediate attention in your collaboration channels.

Why Use the Webex Teams App​

  • Emergency Alerts: Notify security teams instantly in dedicated spaces
  • Incident Response: Coordinate teams during critical events
  • Message History: Persistent message history in Webex Teams
  • Rich Formatting: Support for markdown and attached call data
  • Team Collaboration: Discuss and respond to events in context

Key Features​

  • Space Integration: Post to any Webex Teams space
  • Template Variables: Include dynamic call details in messages
  • Data Attachment: Optionally attach full event data as JSON
  • Markdown Support: Format messages with rich text
  • Bring you own Bot or use Call Telemetry Bot: You can use your own Webex bot token or the Call Telemetry provided bot via Call Telemetry Cloud Connect

Prerequisites​

Before configuring the Webex Teams app:

Configuration Steps​

Step 1: Ensure Organization Bot Setup​

Go to Settings → Organization and the Webex Teams tab panel.

  1. If using your own bot, enter the Bot Access Token from developer.webex.com
  2. If using Call Telemetry Bot, enable Use Call Telemetry Cloud Bot and follow

Step 2: Prepare Your Webex Teams Space​

  1. Create or identify the target Webex Teams space
  2. Add the bot to the space:
    • Click space settings (⚙️)
    • Select "People"
    • Click "Add people"
    • Enter the bot email address
  3. Note the space name and ID for configuration
Getting Space ID

You can get the space ID in several ways:

  • Using the Webex API: GET https://webexapis.com/v1/rooms
  • In the Webex app: Click the space name → Copy space ID
  • Using the List Rooms API with your bot token

Step 3: Create the Webex Teams App​

Navigate to Policies → Apps → Post-Call Apps → Send a Message via Webex Teams Bot

Click Create App

Step 4: Configure Basic Settings​

Fill in the app details:

  • App Name - "Emergency Alerts" or "Security Notifications"
  • Description - Brief description of when messages will be sent
  • App Order - Execution order (80-100 recommended for alert apps)

Step 5: Configure Space and Message​

  • Room Name - Display name of your Webex Teams space
  • Room ID - The space ID where messages will be posted
  • Message Text - Message content with template variables
  • Attach Data - Check to include full event data as JSON attachment

Example emergency message:

🚨 **EMERGENCY CALL ALERT**
**From:** {{ event.calling_number }} ({{ event.calling_name }})
**To:** {{ event.called_number }}
**Location:** {{ app_data.phone-discovery.data.subnet_name }}
**Device:** {{ event.calling_devicename }}

Available Template Variables​

Call Event Data​

  • {{ event.calling_number }} - Calling party number
  • {{ event.called_number }} - Called party number
  • {{ event.calling_name }} - Calling party name
  • {{ event.calling_devicename }} - Device name (e.g., SEP123456789ABC)
  • {{ event.trigger_point_type }} - Where call was intercepted

Location Data Examples (assuming Phone Discovery app runs first)​

  • {{ app_data.phone-discovery.data.phone.ip }} - Phone IP address
  • {{ app_data.phone-discovery.data.phone.extension }} - Extension number
  • {{ app_data.phone-discovery.data.subnet }} - Phone subnet
  • {{ app_data.phone-discovery.data.subnet_name }} - Subnet description
  • {{ app_data.phone-discovery.data.neighbor.neighbor_name }} - Connected switch
  • {{ app_data.phone-discovery.data.neighbor.neighbor_port }} - Switch port

E911 Location Data (assuming Subnet Lookup CSV App with this slug has run first)​

  • {{ app_data.e911-subnet-csv.data.building }} - Building name
  • {{ app_data.e911-subnet-csv.data.floor }} - Floor number
  • {{ app_data.e911-subnet-csv.data.room }} - Room number

Message Formatting​

The Webex Teams app supports standard markdown formatting.

Common Use Cases​

Emergency Call Notifications​

Alert security teams with location details:

🚨 **911 EMERGENCY CALL** 🚨

**Caller:** {{ event.calling_number }} ({{ event.calling_name }})
**Device:** {{ event.calling_devicename }}
**Location:** {{ app_data.e911-subnet-csv.data.building }} - Floor {{ app_data.e911-subnet-csv.data.floor }}
**Address:** {{ app_data.e911-subnet-csv.data.address }}

Attach Data Option - Debug Option​

When "Attach Data" is enabled, the app includes the full event context (including app data) as a JSON code block:. It is primarily useful for debugging only.

{
  "event": {
    "calling_number": "+15551234567",
    "called_number": "911",
    "calling_name": "John Doe",
    "calling_devicename": "SEP001122334455"
  },
  "app_data": {
    "phone-discovery": {
      "data": {
        "phone": {
          "ip": "10.1.2.100",
          "extension": "1234"
        },
        ...
      }
    }
  }
}

Testing Your Webex Teams App​

Using Call Test​

  1. Go to Policies → Call Test
  2. Enter test calling and called numbers
  3. Select the policy with your Webex Teams app
  4. Click Run Test
  5. Check Results:
    • Verify message appears in Webex Teams space
    • Check formatting and variable replacement
    • Confirm data attachment if enabled

Multi-App Workflows​

You can stack multiple apps for enriched emergency notifications.

Emergency Response Workflow​

This flow will discover the phone location and alert the appropriate team in Webex Teams:

  1. Phone Discovery App (Order: 10) - Gather location data
  2. E911 Subnet CSV (Order: 20) - Match to building/floor
  3. SOAP Query App (Order: 30) - Get precise room location
  4. Webex Teams App (Order: 85) - Alert in emergency space

Bot Management​

Creating a Webex Bot​

  1. Go to developer.webex.com
  2. Sign in with your Webex account
  3. Click Create a New App
  4. Select Create a Bot
  5. Fill in the bot details:
    • Bot name (displayed in spaces)
    • Bot username (unique identifier)
    • Icon (optional)
    • Description
  6. Click Add Bot
  7. Copy the Bot Access Token (shown only once!)
  8. Add token to Call Telemetry Organization settings

Bot Permissions​

Webex bots automatically have these scopes:

  • spark:kms - Encrypt messages
  • spark-admin:places_read - Read workspace locations
  • spark-admin:people_read - Read people in your organization
  • spark:messages_write - Post messages in rooms
  • spark:rooms_read - List rooms the bot is in
  • spark:people_read - Access to read your user info
  • spark:teams_read - List teams the bot is in

Other Notification Apps​

Last updated on by Call Telemetry