OTS process map | Bentley Telecom
Bentley Telecom · Internal training

One Touch Switch — process map

Click any step for actions, storage, and example customer emails. Walk the team through match, consent, order, and gated cease.

Match & consent — LIVE Switch / cease order — GATED
Customer Team System (GAS / AWS / MAG) Storage
1

Match check

Customer journey start
Customer
Easy Switching page
Form + light privacy tick
GAS + AWS
Submit match to MAG
Creates BTEL reference
Losing CP
Match confirm / fail
SOR if matched
System
Email + SMS customer
Result + keep reference
Easy Switching page
  • Customer enters name, account, address, current provider
  • Light privacy agreement only (not full order consent)
  • Sees BTEL reference and status while waiting
StorageNothing until submit is sent
Submit match to MAG
  • GAS creates BTEL-YYYYMMDD-XXXXXX
  • Writes Requests + Customers · creates Dynamo case
  • Posts match request via AWS → MAG
Storage Sheet · Requests (Match submitted) · Customers
Dynamo · OtsSwitchCases
Match confirm / fail
  • Losing provider replies via MAG → AWS → GAS
  • Success: SOR valid 31 days · Failure: fault text stored
Storage Sheet · Requests (Matched/Failed, SOR, SOR Expires)
Dynamo · status, switchOrderRef, sorExpires
Email + SMS customer
  • Triggered when match result is processed
  • SMS is a short version of the same message
StorageNote on Requests
2

Consent

Before placing an order
Team
Team portal lookup
Find BTEL on the call
Team
Send consent email
Link on our domain
Customer
Confirm on website
Full GC7.15 wording
GAS
Record consent
Keep ≥ 12 months
Team portal lookup
  • Open internal portal (?portal=1)
  • Look up BTEL · match valid / consent on file
StorageRead Requests + Consents
Send consent email
  • Portal sends via Brevo
  • Button opens bentleytelecom.com/confirm-switch-consent/?ref=BTEL-…
StorageRequests Notes · Consent email sent
Record consent
  • Legal record · means email / website / phone · version gc715-v1
Storage Sheet · Consents
Dynamo · if updateConsent is enabled
3

Fibre order

Same path · OTS flag when switching
Customer
Order on website
Or team takes order
Website
Cookie / bridge
btt_switching_id
Woo → GAS
Order script
Flags Is Switching
Billing
Chargebee + Zen
Normal or pre-order
Order on website
  • After match (and ideally consent), customer can order
  • Live cease still gated until ENABLE_LIVE_SWITCH_ORDER = true
Storage
Cookie / bridge
  • ?switchingId=BTEL-… sets cookie + localStorage
  • Developer must pass into Woo → GAS payload
StorageBrowser · btt_switching_id
Order script
  • Reads switching id · flags Is Switching · can link BTEL ↔ BTF
Storage Pending / Order log · OTS columns
Requests · BTF ID when linked
Chargebee + Zen
  • Same path as a normal order or pre-order
StorageSame order sheets · OTS columns when switching
4

Later — switch / cease

Not live until flag is on
System
Committed date
From Zen fulfilment
Gated
Switch / cease order
Needs SOR + consent
Committed date
  • Often after order · used to align cease with new start
StorageRequests · Committed Date
Switch / cease order
  • Only when ENABLE_LIVE_SWITCH_ORDER = true
  • Requires valid SOR (31 days) + consent on file
StorageRequests Cease Status · MAG · Dynamo
Where things are stored
WhatGoogle SheetDynamoElsewhere
Match (BTEL)Requests, CustomersOtsSwitchCasesAWS / MAG
SOR + expiryRequestsYes
GC7.15 consentConsentsIf wired
Fibre order (BTF)Pending / Order logLink on caseChargebee, Zen
Switching ID in browserCookie + localStorage
Team phone script

When a customer calls about switching

  1. Confirm BTEL reference (or run match on Easy Switching with them).
  2. Open team portal → look up BTEL → check match still valid.
  3. Send consent email (customer confirms on bentleytelecom.com).
  4. When ordering → site order with switching cookie, or attach BTEL manually.
  5. Do not promise instant cease of the old service until the live switch flag is on.
Portal: your GAS /exec URL + ?portal=1 · internal only.
Bentley Telecom · OTS training · Match & consent live · switch order gated