Skip to main content

Platform overview

imatic is one platform with three products — Voice Portal, Calendar, and Survey. They look and feel different because they serve different jobs, but they share the same foundations: how you sign in, how you authenticate API calls, how you receive webhooks, and how AI agents connect over MCP. This page maps those shared pieces so you know where each product lives and what carries over between them.

The three products​

ProductWhat it doesAccount model
Voice PortalAI voice-calling agents, campaigns, contacts, call logsOrganization (team)
CalendarShareable booking links, calendar sync, appointmentsIndividual
SurveyForms and surveys, responses, live analyticsIndividual

Each product has its own introduction: Voice Portal, Calendar, and Survey.

Accounts and organizations​

How you're organized depends on the product:

  • Voice Portal is organization-first. When you sign up, you create an organization and become its admin. Inside the org you group work into Projects, and projects contain Agents. You invite teammates and give them roles. See Sign in & organizations.
  • Calendar and Survey are individual-first. You sign up as a person and start working immediately — your own booking links or your own forms. Both products still support inviting people and admin roles where you need a team around your account.

Roles​

All three products use a role hierarchy, from a platform-level super admin down to a normal user with view and limited-edit access. Voice Portal adds an org admin (the owner) and a project manager (scoped to a project). Calendar and Survey use the same broad shape, scaled to an individual account.

Shared concepts​

These four ideas work the same way across every product. Learn them once and they carry over.

Authentication​

You sign in to each product's web app with your email and password (Calendar also offers Google and Outlook sign-in). Behind the scenes the app uses a JWT for your session. For programmatic access you don't use your password — you create a scoped API key instead. See the REST API page for both.

API keys​

Each product lets you create API keys to call its REST API. A key is shown in a prefix.secret form, carries scopes that limit what it can do, and is shown only once at creation. You manage keys in each product's developer area.

API keys are secret

An API key grants access to your data. It is displayed only once, when you create it — copy it then and store it somewhere safe. Never commit a key to source control or paste it into a public place. If a key leaks, revoke it and create a new one.

Webhooks​

Instead of polling, you can register a webhook so imatic notifies your server when something happens — a booking is created, a response is submitted, and so on. Webhook deliveries are signed with HMAC so you can verify they genuinely came from imatic. See webhooks in the REST API guide.

MCP for AI agents​

imatic exposes Model Context Protocol (MCP) servers so AI assistants can read and act on your data with the right permissions. The credential differs by product: Calendar's MCP authenticates with a scoped API key carrying the mcp scope; Survey's MCP authenticates with your portal JWT; Voice Portal instead lets you register external MCP servers for your agents. In every case calls stay within your organization's isolation. See MCP for AI agents.

Where each product's API lives​

The shared concepts above are the same everywhere, but each product exposes its own resources. Start from the product's developer page for endpoint names, payloads, and examples:

  • Calendar — event types, availability/slots, bookings, calendars, webhooks, API keys, and a 7-tool MCP server. See Calendar for developers.
  • Survey — forms, responses, aggregation, AI form generation, webhooks, and MCP tools. See Survey for developers.
  • Voice Portal — agents, tools, and MCP server registration for connecting external tools to your agents. See Tools & MCP for agents.

Languages​

The imatic apps and these docs are available in 13 languages, including right-to-left rendering for Arabic and Urdu. Switch using the language dropdown in the top navigation. See Languages & RTL.

Getting support​

  • Start with these docs — most pages end with Next steps or Related links to take you deeper.
  • Voice Portal organizations can raise a request in the in-app Tickets area.
  • For account or billing questions, use the support contact details shown inside your product's settings.