Sepal Concierge

One life event first. Then one agency at a time.

Rollouts start with the agency that operates the front door and one journey residents ask about most — usually moving in — and grow partner by partner. Each phase ends with something your team signs off on.

  1. Stand up the front door

    Your organization, single sign-on and roles, the orchestrating agent, guardrails and the channels you want first: the website, the widget, SMS or a kiosk.

  2. Build the operator’s agent

    Connect the operator agency’s pages, forms and address services. Its agent becomes the replicable blueprint for every agency that follows.

  3. One life event, end to end

    Moving in, starting a business or buying a home: the checklist, the partner steps, the consent wording and the pre-filled forms in the sandbox.

  4. Languages

    Native-speaker review of interface strings and the glossary for each of the nine languages, then the language-parity evaluation set.

  5. Bring partners on

    Each partner agency follows the same path, below. Stubs keep the resident experience consistent while real agents are built.

  6. Train

    Every role has its own path in the Sepal Concierge Academy — program lead, service designer, content steward, agent engineers, contact center, reviewers, privacy, language access, planner and executive — with exercises in the sample region.

Bringing partners on

A partner agency joins with its own agent, on its own schedule. The federation roadmap and cost model in the console show where each one is and what the next phase costs.

StepWhat it coversWhat it produces
Readiness assessmentData, APIs, identity, security, hosting, staffing and governance, scored with the partner’s IT teamA recommended path, effort in weeks and a support tier
Data-sharing agreementWhich details may go to the partner, for what purpose and for how longThe data-sharing matrix the orchestrator enforces
Stub or starter agentThe Python ADK kit or a stub that answers from public pagesAn agent in sandbox with a published agent card
Conformance and registrationThe twelve-check suite, then the registration approval routeA live agent on the front door
Knowledge and evaluationThe partner’s allow-listed pages and evaluation questions in nine languagesCited answers and a language-parity score

How long it takes

The front door with the operator’s agent and one life event typically takes eight to ten weeks, most of it content and language review. A partner with an existing agent can join in two to four weeks; a partner starting from the Python kit in six to eight.

Talk to us about your rollout