Implementation layer
Run cloud phone workflows through guides
Guide pages should help teams move from "what should we use" to "how should we actually run it" across APIs, reusable templates, profile state, and per-account routing.
Build
Translate decisions into operating steps
Repeat
Make execution reusable
Connect
Route back into the right product layer
APITemplateRouting
Guide board
GUIDE_ACTIVE
What the guide layer is responsible for
01
Scope
Translate product decisions into operating steps and reusable structures.
02
Format
Show teams how to run APIs, templates, sync, and routing as systems, not isolated tricks.
03
Route
Push users back toward the right product and use-case pages when deeper context is needed.
Guide entry points
Four operating guides teams actually use
Guide 01
Cloud Phone API
How APIs fit orchestration, workflow control, and operator-facing automation.
Role
Integration guide
Guide 02
Mobile RPA Templates
How template-driven automation helps standardize recurring mobile operations.
Role
Automation guide
Guide 03
Profile Sync
How synchronized account state supports cleaner multi-operator workflows.
Role
Workflow guide
Guide 04
Proxy IP per Account
Why per-account routing matters for isolation, stability, and regional execution control.
Role
Network guide
What users should leave with
Guide Pillar
A runnable structure
Users should leave with a workflow structure they can actually organize around.
Guide Pillar
A repeatable pattern
Good guides explain how to make execution reusable instead of one-off.
Guide Pillar
A next step
Guide pages should always connect back to product pages and use-case pages.