The platform

The Instaconnect platform — chat, booking, video and events in one workspace

Chat, scheduling, video, events and meeting-level recordings can be configured in one tenant with shared workspace roles. Each product still has its own workflow, records and limits; a universal customer record is future scope. Commercial terms are scoped in a written proposal.

Book a demo What’s supported today

Illustration of three Instaconnect modules — chat, calendar and stage — connected by light ribbons

Four products

Four products, one workspace.

Widget module

InstaSupport

Answer a website question from approved material, then hand the conversation to an available person when needed.

Website chat, content-grounded answers, configured human escalation, browser video and public ticket creation and lookup. Co-browsing is future scope.

Full guide

Calendar module

InstaCall

Qualify a booking request, route it to a configured team and rehearse confirmation, cancellation and rescheduling.

Scheduling built into the workspace: event types, team round-robin, routing forms, and Google / Microsoft calendar connections.

Full guide

Events module

InstaMeet

Build a branded programme and registration path, rehearse the event, then assign session and follow-up owners.

Run virtual conferences from one workspace: branded landing pages, agenda, registration, sponsors and live sessions.

Full guide

Recordings & AI module

InstaStudio

Record a selected supported meeting or session, review the transcript and approve the summary before follow-up.

Meeting-level recordings, speaker-labelled transcripts and generated summaries for selected supported calls and event sessions, with human review before follow-up.

Full guide

Shared workspace

What the products share

One tenant and role model

Products can share a tenant and workspace roles. Access still needs review for each selected workflow.

Connected starting points

A website conversation can lead to supported booking or browser-video steps when those paths are configured.

Separate operational records

Do not assume one universal inbox or customer record across chat, tickets, bookings, events and recordings.

Review integrations Review availability Review trust

Evaluation and rollout

Prove one supported workflow before expanding.

01Choose one starting workflow and name its human owner.
02Confirm the content, routing, roles, permissions and fallback the team must prepare.
03Check current availability, integration boundaries and trust requirements against that workflow.
04Rehearse the full path with your team before opening it to visitors or attendees.
05Record supported scope, future scope and commercial terms in the written proposal.

LET'S CONNECT

Walk through one supported workflow.

Book a demo and we'll review the modules that fit your team, with future-scope items kept separate.

Book a demo Discuss your workflow