Puestario
Security & dataSee live agentsSign up for a call
Menu

From a voice note to a useful team answer.

See how Emily and SPARX help run Son Hábitos, our Spanish-language coaching business: a voice request, a useful report, a closer look at the data, and a handoff the team can act on.

An internal operating case from the founder’s own business. This is not an independent customer testimonial.

By Puestario · Gerardo "Lalo" Vera

01 / Ask. Follow up. Understand.

A voice note opens the conversation.

Lalo asks for an overview, narrows the question, then opens one person’s record. Emily brings the information back into the same chat.

From the actual conversation

The original overview, in WhatsApp.

A seven-second voice message is followed by Emily’s report. This screenshot contains aggregate program figures; individual client records are not shown.

Original Spanish WhatsApp exchange: Lalo’s seven-second voice message and Emily’s program-level weight report, with reporting-period and excluded-data notes.
Open full-size screenshot ↗

Original screenshot supplied by the founder, September 21, 2026. Its reporting window and cohort totals need reconciliation; the figures are not validated outcomes or results caused by an agent.

Recreated from the supplied exchanges. Requests are paraphrased; all client labels, measurements and chart values below are fictional teaching data.

  1. 01

    Start with the whole team.

    Ask the question in everyday language. Emily’s captured response groups the report by program and notes missing or excluded data.

    What the agent does

    Reads the available records and turns them into an overview the coach can review.

    EmilyA workflow from Son Hábitos
    Lalo · voice request

    Give me an overview of our clients.

    Request paraphrased from the owner’s account. Audio is not published.
    Emily

    Here is the report, organized by program.

    Who submitted an update
    Who is missing an update
    Which changes need a closer look

    Keep the reporting period and missing data visible.

  2. 02

    Follow up with a focused question.

    The next voice message asks who gained weight. The actual exchange shows a read-only query comparing each record’s latest measurement with a previous measurement, followed by a filtered list.

    What the agent does

    Compares existing data, calculates the change and returns the records that match the question.

    EmilyA workflow from Son Hábitos
    Lalo · voice request

    Who gained weight over the last two weeks?

    Request paraphrased from the owner’s account. Audio is not published.
    EmilyRecords with an increase
    Fictional data · weight in lb
    RecordPreviousLatestChange
    Client A ↗178180+2
    Client B162163+1
    Client C151151.5+0.5

    A missing measurement is missing data, not zero change.

  3. 03

    Open the context behind one result.

    One more question brings back a record summary, recent notes and a graph. The original contains personal details; this example shows the structure using fictional information.

    What the person does

    Reviews the history, checks the source and decides how to follow up. Emily retrieves the context; the coach provides the coaching.

    EmilyA workflow from Son Hábitos
    Lalo · voice request

    Show me the full picture for Client A.

    Request paraphrased from the owner’s account. Audio is not published.
    EmilyClient A · example record
    Latest measurement
    180 lb
    Previous measurement
    178 lb
    Recent note
    A follow-up conversation is due.
    Six recorded measurements · fictional data
    182180179177178180Oldest → latest

02 / Move the work forward

A sale becomes a team handoff.

The supplied sales screenshot shows the team sharing an intake, SPARX organizing it, and Emily acknowledging registration. The next action stays visible: activation is still pending.

Reconstruction of a real handoff. Client, medical, contact and payment details omitted.

  1. 1Sales team

    Intake shared

    A team member posts the new registration details in the staff chat.

    New enrollment + orientation information
  2. 2SPARX

    Handoff organized

    SPARX formats the intake, includes orientation details and tags Emily.

    Structured summary → Emily
  3. 3Emily

    Registration acknowledged

    Emily confirms the record and explicitly leaves activation to the team.

    “Queda sin activar: no le llega nada hasta que le pongan la llave en el panel.”

The boundary is part of the work. The message says the client remains inactive and receives nothing until the team activates the record in the panel.

03 / Keep the owner informed

SPARX connects reports with the owner’s day.

The screenshots also show Emily reporting on her week and SPARX acknowledging that the report was archived. SPARX separately describes scheduled ads reporting, research and operational alerts.

The weekly handoffBased on the supplied screenshots
EmilyWeekly activity report

September 14–20, 2026

Record lookups and coach notes
Requested updates and follow-ups
Scheduled notices and reminders
SPARX

“Archivado: Reporte Emily · 14-sep al 20-sep-2026”

Message excerpt; private storage location omitted.
Described by SPARX · illustrative report

The morning ads brief

SPARX describes pulling Meta Ads data, calculating cost per lead and sending a campaign summary to Lalo. These are fictional figures showing what that report helps someone compare.

Fictional campaign data · USD
CampaignAd spendLeadsCost / lead
A$12015$8
B$14010$14
The owner decides what changes.

A report can flag a difference. Pausing or scaling a campaign still requires the owner’s instruction.

An original ads-report screenshot and API export were not supplied. This panel explains the reported workflow; it is not a captured delivery or a claim of better ad performance.

The work behind the question

Our team needs answers from records it already keeps: who submitted an update, what was noted previously, and which follow-up is due. Finding those answers can interrupt coaching and create another status request for a colleague.

Gerardo “Lalo” Vera reports using two agents internally for approximately eight months. A technician maintains and develops them, while Lalo oversees how they work. Emily supports the coaching team; SPARX supports the owner’s reporting and coordination.

Defined actions. Human responsibility.

Emily’s described setup separates read-only database queries from named operations for specific requested updates. A captured sales handoff shows Emily acknowledging a new record while explicitly leaving activation pending. Preparing information does not automatically authorize the next business action.

The team remains responsible for coaching, reviewing exceptions, and approving changes outside the agreed task. Emily reports missing information or tool failures rather than treating an empty record as completed work. Those rules must also be checked in the actual tools and permissions.

What we can show, and what we still check

The owner supplied six screenshots: a sales handoff, the lookup conversation, and a weekly activity report for September 14–20, 2026. These show actual responses and reported activity. They do not independently verify every database write or message delivery.

We are not publishing hours saved, a success percentage, or a return-on-investment figure. Report periods and counting rules need reconciliation before their totals become performance claims. A useful test checks answers against the source, including missing data and exceptions.

Bring one question your team keeps asking.

Describe what people keep looking up, where the information lives, and who needs the answer. In an English or Spanish demo, we can discuss a bounded first task and what a person should review.

Sign up for a call