Connect Migration Workshop
2 hours · Free

Two hours with FlowShift and ComplianceGen running on your actual source platform, with the solution architects who would lead the migration in the room.

FlowShift runs on your actual Genesys, Avaya, or Cisco platform for the full two hours. You see the per-flow conversion rate, the exceptions flagged with the reason FlowShift refused to auto-convert them, and a per-flow diff your QA team can sign off. ComplianceGen reads one of your compliance documents and ships the Contact Lens config built from it, clause references on every rule. The room is run by the solution architects who would lead the migration, not by sales.

2 hours Free to attend FlowShift + ComplianceGen live Engineers run it Remote or on-site

Why this workshop exists

Most Connect migration plans are built on guesses about flow complexity, compliance scope, and total cost.
This workshop replaces all three with measured numbers off your own platform.

FlowShift analyses your actual flows and produces the conversion report. ComplianceGen reads one of your actual compliance documents and ships the Contact Lens config built from it. Both run live during the session, not in a video.

$50k MDF

Available from AWS for Amazon Connect implementations. Connect Customer engagements are eligible. We cover MDF and MAP availability during the workshop.

75-80% auto-converted

Of legacy flows convert automatically. You see FlowShift run live during the workshop and watch the conversion report build in real time.

1 day vs 2 weeks

Compliance configuration from source documents. ComplianceGen generates every keyword list, pattern match, sentiment trigger, and evaluation form in a day. Not two weeks of manual console work.

What happens in 2 hours

Five sessions in two hours, both demos on your actual migration risk surface rather than on a reference architecture.

0:00 – 0:2020 min

Why migrations take longer than planned

The patterns that cause overruns, and what the automated alternative looks like. Data from real engagements, not slides.

0:20 – 1:0040 min

FlowShift live demo Live Demo

Migration analysis on a real contact centre environment. Config inventory, flow analysis, conversion report. Flows that convert, flows flagged with reasons. AI injection recommendations. KB migration output. TCO calculator.

1:00 – 1:2020 min

ComplianceGen live demo Live Demo

Reads a real compliance document (FCA or HIPAA). Generates all rules clause-referenced. Deploys the configuration via API. You watch the entire process from document to production-ready config.

1:20 – 1:4020 min

Facilitated assessment

Apply the tools to your own migration. Discuss your flows, your compliance obligations, your timeline. Engineers answer every technical question.

1:40 – 2:0020 min

Open Q&A + path forward

MDF funding eligibility. Phased migration approach. Multi-jurisdiction compliance. Genesys QA form preservation. Whatever you need answered before committing to a programme.

What you see during the demos

Both demos run live on your platform and your documents, not on a reference dataset.

FlowShift

Main IVR trunk: converted, 847 lines JSON

Payment handling: converted, Lex bot recommended

Account query: converted, Q in Connect recommended

Claims escalation: flagged, CUCM trunk dependency

Callback scheduling: flagged, Lambda rewrite needed

78% converted
22% flagged
100% AI recommendations

TCO: Current Genesys £420k/yr → Connect £118k/yr
3yr saving £906k

ComplianceGen

Keyword list: Vulnerable customer, 24 terms, FCA PRIN 2A.3.4

Real-time alert: Mandatory disclosure 3 min, FCA COBS 2.2.1R

Sentiment trigger: Escalation risk 90s, Internal QA Policy 4.2

Pattern match: Payment arrangement, 18 phrases, FCA CONC 7.3.4

Eval form: 10 questions, AI scoring

47 rules
All clause-referenced
Deploy: 3 minutes

What you leave with

Six things. Concrete. Yours.

Seen FlowShift analyse real contact flows and produce a conversion report with flagged items and AI recommendations

Seen a compliance configuration built in real time from a real regulatory document, clause-referenced and deployable

A rough assessment of your own migration complexity based on the facilitated discussion with Armakuni engineers

Clarity on AWS MDF funding eligibility and how it applies to your Connect migration programme

Answers to every technical question from engineers who have run these migrations, not sales consultants

A scoped proposal if you are ready, or a clear next step if you need more information first

Two hours with FlowShift and ComplianceGen running on your actual source platform, with the solution architects who would lead the migration in the room.

Most Connect migration plans are built on guesses about flow complexity, compliance scope, and total cost.
This workshop replaces all three with measured numbers off your own platform.

Five sessions in two hours, both demos on your actual migration risk surface rather than on a reference architecture.

Both demos run live on your platform and your documents, not on a reference dataset.

Six things. Concrete. Yours.

Four roles. Two hours.
Every question answered.

How we helped real customers ship on AWS.

Two hours. Your migration risks.
Answered before you commit.

Two hours with FlowShift and ComplianceGen running on your actual source platform, with the solution architects who would lead the migration in the room.

Most Connect migration plans are built on guesses about flow complexity, compliance scope, and total cost.This workshop replaces all three with measured numbers off your own platform.

Five sessions in two hours, both demos on your actual migration risk surface rather than on a reference architecture.

Both demos run live on your platform and your documents, not on a reference dataset.

Six things. Concrete. Yours.

Four roles. Two hours.Every question answered.

How we helped real customers ship on AWS.

Two hours. Your migration risks.Answered before you commit.

Most Connect migration plans are built on guesses about flow complexity, compliance scope, and total cost.
This workshop replaces all three with measured numbers off your own platform.

Four roles. Two hours.
Every question answered.

Two hours. Your migration risks.
Answered before you commit.