- Client
- Agência OKSE (Xanxerê, Brazil, founded in 2020)
- What we did
- New company website with native SEO and GEO, measurement installed in the client account, and an AI agent triaging WhatsApp, all deployed in an eight hour on site immersion
- Platform
- Site on Next.js 15 + Tailwind on Vercel · Triage agent on Balcão, an Epicora product
- 8 hours
- one Friday inside the agency: walked in with no new site and no measurement, walked out with the site live on its own domain, measurement running and the agent answering
- 14 live pages
- in the new sitemap, submitted and processed the same day; on the old site, ten portfolio pages returned errors and eight fictional profiles were still indexed from 2019
- 0 to 4 events
- from no measurement at all on their own site to WhatsApp click, form submission, phone click and case view, marked in the client account
- Became a product
- the agent built to answer OKSE gave rise to Balcão, an Epicora product; on 8 September 2026 the agency migrated onto it and stopped maintaining its own server
The starting point
OKSE sells digital presence to its clients and was not measuring its own. The website existed, but had no measurement installed at all: no analytics, no tag manager, no heatmap. Without that there is no way to know whether the site brings anyone in, so the agency reported client results with numbers and its own results with impressions.
The site also carried leftovers from an old theme nobody had audited. Ten portfolio pages returned errors while still listed in the sitemap and linked from the home page, because the content type had dropped out of the registry. And the sitemap indexed eight fictional team profiles that shipped with the theme, with invented names, live since 2019. That is what a site accumulates when it belongs to everyone and to no one.
The other front was the front door. Every new contact arrives on WhatsApp, and was answered by whoever happened to be free, with no triage and no record. On a team of five serving 17 clients, that means first response depended on somebody having their phone in hand, and nothing that came in stayed organised afterwards.
- No measurement installed on their own site: no analytics, no tag manager, no heatmap.
- Ten portfolio pages returning errors, still listed in the sitemap and linked from the home page.
- Eight fictional team profiles from the old theme, indexed since 2019.
- A front door with no triage: every contact landed on WhatsApp and was answered by whoever was free, with no record.
The turning point
Both fronts were real construction, and neither is solved by sending a link. A new site needs content decisions from whoever knows the business, and a triage agent needs the team to trust what it answers before it is allowed in front of a client.
That changed the shape of the delivery. Instead of selling both fronts and negotiating each one, Epicora proposed one day: two people inside the agency, ten in the morning to six in the evening, with the site and the agent built beforehand and only published on the day. The whole day went to what only works with the client in the room.
A deployment, not a delivery over the wall. The site was adjusted live, with the owner beside us, in three rounds on the same day: the artwork he sent became the hero, the video testimonials from his clients went into the right sections, and the positioning was rewritten with him reading the screen. The immersion landed on a Friday on purpose, so the weekend would be the first real test without Epicora in the room.
Build beforehand and deploy together. Everything that is code was done outside the day, finished and tested; the day itself went to what no software solves, which is the content decision and the team trusting the agent. New site live and triage answering before the first weekend.
What we delivered
01 · A website that works
Company website rebuilt from scratch, with SEO and GEO from the start rather than patched in later: complete structured data, a lean sitemap with 14 live pages, canonicals, and the redirects from the old site checked one by one, so the ten pages returning errors stopped existing instead of staying indexed.
02 · Measurement, born with the site
Tag manager, analytics and heatmap installed on the day, all in the client own account, with the four events that matter to an agency marked with parameters: WhatsApp click, form submission, phone click and case view. The agency now gets from its own site the same kind of reading it delivers to clients.
03 · The front door, answered
An AI agent that answers first contact on the agency WhatsApp. It was written from the official site material, not improvised: positioning, the six services, the real frequently asked questions and only the true case studies. It invents no pricing, promises no deadline, and hands the conversation to a person when the subject leaves what it knows.
04 · The agent became a product
The OKSE need did not end in a one off install. It gave rise to Balcão, an Epicora product for WhatsApp intake triage, with a dashboard, a pipeline and a conversation record. On 8 September 2026 the agency migrated onto it as a tenant and stopped having its own server to maintain. What started as one client delivery became a product, and the client kept the product.
How we made it hold
The account belongs to whoever accumulates the history
The rule was written before the first account was created: any asset that accumulates history or identity lives in the client’s account, with our access (domain, analytics, tag manager, Search Console, Google listing, business manager). Plumbing a successor could swap in minutes lives in ours. That ruler is what decided analytics would sit in the agency’s Google account and not in ours: the site’s privacy policy declares OKSE as the data controller, and the architecture has to agree with the document.
No number that cannot stand up
The material the client sent carried a "+247% in sales". It did not make the cut, because it is a number with no origin. His clients’ video testimonials did make it, and there the number is spoken by the person themselves, on camera, never written into the copy. The same criterion took the address and the tax ID off the site, at the owner’s request, and fixed the founding year, which was wrong on the old site and aged on its own.
A go-live that never touched what could not stop
Form delivery was built on a sender Epicora had already verified, on purpose: that way not a single DNS record on the agency’s domain is touched for the form to work, which removes the riskiest step of the day, editing the zone where the agency’s email lives. During the DNS migration, email survived the cutover, verified on the spot. And the site went through an approved manual quality review before shipping, with automated checks in the repository.
What stood up, and what we are not measuring yet
What the immersion proved is the format more than the technology: build beforehand and deploy together shortens go live to a single day and leaves the client operating what they received instead of merely receiving it. Site live on its own domain, measurement running, agent answering, and the following weekend as the first real test, all on the same Friday. The remaining adjustments closed the week after.
The follow on is the rarest thing in this case. The OKSE front door was a specific problem of a small agency, and its solution became a product: Balcão came out of that pilot and today serves more than one client. The agency that originated the product stopped carrying its infrastructure and became a tenant, with its own server shut down.
And a frank note about numbers. The measurement accounts stayed, by design, in the agency own account. That is the right call for the client and it has a price for us: Epicora has no reading of traffic, contacts or conversations on the OKSE side, and will not publish an estimate in place of a measurement. This case closes on verified delivery, not on traction numbers, and that is deliberate.
Does your site measure nothing while every enquiry lands on WhatsApp?
This is the kind of problem Epicora solves in deployment, not in a quote: built beforehand, then one day inside your company so the team walks out operating it.