Skip to content
Point of Contact

Overview

PointOfContactAI is a chat triage product for customer support teams. Visitors talk to an AI assistant via an embedded widget on your website. When a conversation needs a human, an agent in your support team picks it up from a Microsoft Teams personal tab — they read the existing transcript and take over the chat in real time.

Who it’s for

  • B2B SaaS support teams that want AI-first triage with predictable per-seat pricing.
  • Companies that need to keep customer conversation data inside their own Azure tenant (compliance, data residency, BYOK).
  • Teams already on Microsoft 365 / Teams who don’t want yet another agent console.

How it’s structured

Every paying customer gets a fully isolated Azure stack deployed into their own subscription:

  • Cosmos DB (serverless) — chat sessions + messages + token usage
  • Azure OpenAI (gpt-5-mini) — the AI assistant
  • SignalR Service (Free tier) — realtime visitor ↔ bot ↔ agent
  • Key Vault — admin keys + AAD app secrets
  • Function App (Flex Consumption) — the customer-runtime code

The PointOfContactAI vendor (the “ISV control plane”) only knows your subscription id, plan, and seat count — never your conversation content. Two content-free callbacks per hour (seat-report + deploy-status) are the only outbound traffic from your stack to ours, and both are strictly schema-validated at the boundary.

You own the infrastructure. Every resource runs in your Azure subscription, so your cost is two separate charges: (1) the per-seat plan license ($49 / $99 / $199) via Azure Marketplace, and (2) the Azure infrastructure (~$3–120/mo depending on plan, plus pay-as-you-go AI tokens) billed to you directly by Microsoft. The plan license does not include the Azure infrastructure cost. See Resource tiers & sizing.

What you’ll do

  1. Check the prerequisites — Azure roles, Teams admin rights, OpenAI quota.
  2. Buy from the Marketplace — pick a plan, complete checkout.
  3. Deploy via the portal wizard — ~5 minutes.
  4. Set your admin key — a fresh deploy has none; the first rotation creates it.
  5. Set up the AAD app for Teams SSO (one-time script run + support request), then sideload the Teams app into your Teams tenant.
  6. Embed the widget on your site.
  7. Operate — the dashboard shows live cost, seat usage, and grace-period state; runtime updates arrive without any action from you.

Next

  • Quick start (5 min) — buy → deploy → first chat.
  • Concepts — control plane, customer stack, agent ↔ visitor messaging model.