Blocker 44 · Business

Launching a new brand takes months: new lines of business from reusable parts on Amazon Connect

The marketing plan is ready and the website is live, but customers have nowhere to call. On Amazon Connect, a new line of business can be built mostly from parts you already run: a new number, a new queue, and the flows you trust.

Illustration. The blocker: A new line takes months to launch. The fix: Reusable building blocks for each launch.

The blocker

The business has acquired a company, launched a new product line, or opened in a new region. Sales and marketing are ready. Then someone asks where customers will call, and the answer is “the contact center team needs three months.”

Every week of delay has a price. The launch goes out with an email address instead of a phone number. Customers of the new brand call the old number and reach agents who know nothing about it. Or the launch date simply moves. Leaders start to see the contact center as the thing that slows the business down.

Why it happens

  • Every line is built from scratch. The existing IVR was built by hand for one brand, so the next one means copying it and editing hundreds of settings.
  • Numbers take time. Ordering and porting numbers through a carrier runs on its own timeline.
  • Hours and holidays are hard-coded. Opening times live inside flows, so a new time zone means new flows.
  • Changes are manual. Nobody can reproduce the configuration reliably, so every launch carries risk.

How Amazon Connect solves it

Amazon Connect lets you treat a line of business as a set of small, reusable parts. Build the shared parts once, and a new brand becomes mostly new values.

1. Get a number today, port the old one in parallel

In the admin website you can claim a toll-free or DID number, and in the US choose the area code. The same can be done in code with SearchAvailablePhoneNumbers and ClaimPhoneNumber. You then attach the number to a flow.

If the brand already has a number customers know, start porting early. In the US and Canada it typically takes two to four weeks after portability is verified and documents are correct, and longer in other countries. Use a claimed number for building and testing while the port runs.

2. Build shared logic once with flow modules

Flow modules are reusable sections of a flow, with their own inputs, outputs and branches. Put greeting, caller identification, payment and routing logic in modules, and every brand’s flow calls the same ones. When you fix a module, you can propagate the change to every flow that uses it.

Each brand then needs only a short entry flow. AWS gives this exact example for the Set contact attributes block: define an attribute for a company name or line of business and use it in text-to-speech. Brand-specific recordings and hold music are prompts you upload.

3. Keep brand settings in data tables, not in flows

Data tables store configuration as rows and columns that flows read at runtime. AWS gives an example of mapping each store location to its business hours and support queue. Changes take effect almost immediately, without editing the flow. For a new brand, that means adding a row: its queue, its greeting, its escalation number.

4. Queues, hours and routing in minutes

Create a queue for the brand and give it hours of operation in its own time zone, with overrides for holidays. The Check hours of operation block reads those hours and can branch on overrides, for example to play a holiday greeting. Add the new queue to existing routing profiles so trained agents can take its contacts from the first day, then build a dedicated team as volume grows.

5. Make the next launch a template

Amazon Connect resources such as queues, hours of operation, flows, flow modules, routing profiles, phone numbers, prompts and users have AWS CloudFormation resource types. We build a template for a line of business, with the brand name, time zone and number type as parameters, and release it through a pipeline. Flows can also be imported and exported between instances and Regions. Tag each brand’s resources so you can find them, report on them and control who can change them.

The template is custom work, not a built-in Amazon Connect feature. Our posts on separate dev, test and production and manual changes that break production cover how to run it safely.

What good looks like

A new line of business starts with a short request: brand name, time zone, hours, number type and the team that will answer. The number is claimed the same day. The configuration is deployed to test from the template, checked, and promoted to production. Customers of the new brand hear its name from the first call, and the team handling them uses the same desktop and reports as everyone else. The contact center is ready before marketing is.

Where to start

  1. List what differs between your current lines of business: names, hours, queues, prompts and escalation numbers. Everything else is shared.
  2. Move the shared logic into flow modules, and the differences into a data table.
  3. Describe one existing line of business in a CloudFormation template and deploy it to a test instance.
  4. Use that template for the next launch, and measure how long it takes from request to first call.
High-level architectureA new line of business from reusable parts
New brand customers
  • New number
  • Web chat
Phone numbers
  • Claim a number
  • Port a number
Shared building blocks
  • Flow modules
  • Data tables
  • Prompts
Brand setup
  • Queue
  • Hours of operation
  • Routing profiles
Template
  • CloudFormation template
  • Release pipeline
Agents
  • Existing team
  • New brand team
  • People
  • Amazon Connect
  • Built by Digiclarity
  1. The brand gets a phone number the same day: claim a toll-free or local number, and start porting an existing one if the brand already has it.
  2. A short brand entry flow sets the brand name and line of business as contact attributes, then calls the shared flow modules for greeting, authentication and routing.
  3. A data table row holds the brand's hours, queue and settings, so flows read them at runtime instead of being copied and edited.
  4. A new queue with its own hours of operation and holiday overrides is added to existing routing profiles, so trained agents can take the new brand's contacts from day one.
  5. All of it is described in a CloudFormation template that we build, so the next brand is a new set of parameters, released through the same pipeline.
References

Official AWS documentation

Every Amazon Connect capability in this post links to AWS’s own documentation, so you can check the details for your Region and account.

  1. Get a local toll-free or DID phone numberdocs.aws.amazon.com
  2. SearchAvailablePhoneNumbers APIdocs.aws.amazon.com
  3. ClaimPhoneNumber APIdocs.aws.amazon.com
  4. How long does it take to port phone numbers?docs.aws.amazon.com
  5. Attach a claimed or ported phone number to a flowdocs.aws.amazon.com
  6. Flow modules for reusable functionsdocs.aws.amazon.com
  7. Create and configure data tablesdocs.aws.amazon.com
  8. Flow block: Set contact attributesdocs.aws.amazon.com
  9. Create promptsdocs.aws.amazon.com
  10. Create a queuedocs.aws.amazon.com
  11. Set the hours of operation and time zone for a queuedocs.aws.amazon.com
  12. Flow block: Check hours of operationdocs.aws.amazon.com
  13. Create a routing profile to link queues to agentsdocs.aws.amazon.com
  14. Amazon Connect resource types in AWS CloudFormationdocs.aws.amazon.com
  15. Import and export flowsdocs.aws.amazon.com
  16. Add tags to resourcesdocs.aws.amazon.com
Start here

Tell us what you want to improve.

We will tell you whether a voice agent fits it, what it would take, and what it should return. You will hear back within a week.

  • AWS Advanced Tier Services Partner
  • AWS Migration Services Competency
  • Amazon Connect Delivery Partner
  • AWS AI Services Competency
  • AWS Experience-Based Acceleration (EBA) partner
  • ISO/IEC 27001 certified
  • SOC 2 Type II
Certified supplierMWDBE certifiedTexas HUB certifiedNCTRCA certified
+1 (214) 550-14936275 West Plano Parkway, Suite 500, Plano, Texas 75093