Briefs
Briefs asks your questions for you, on a schedule, and tells the right people what
needs a decision. Each persona gets a weekly brief with one tap, and you can schedule any
question of your own. Open it with Briefs, under Fetch in the rail
(/active_schedules). The page is titled Weekly briefs.
A brief is an ordinary run of FACE, asked at a set time or when your data changes. Its answer, options and decisions land on Ask, Options, Why and Actionable Twins like any other run.
Weekly briefs
The top of the page lists one row per persona of this instance: the product’s five (Field operations manager, CFO, CRO, CMO and CEO) and any your instance added. Each row shows the question its brief asks and the persona’s plays. Your own persona, set under Settings › Account, is listed first and marked Yours.
- Add brief schedules that persona’s brief. It runs every Monday at 07:00 on this device’s clock, and is sent on WhatsApp to the numbers in Settings › Integrations › Channels. Once added, the row reads Added · next run {next}, or PAUSED.
- Edit opens the persona editor, the same one as Settings › Personas. Add persona adds a new one. What you save is shared with everyone on the instance.
- Ask FACE as {name} opens the assistant for that persona, with its question first.
Deadline watch is not a persona. It asks every day at 07:00 which claim windows close in the next 3 days, and what evidence each still needs.
If the instance’s personas cannot be read, the page says so and lists the product’s five in the product’s own words.
Your briefs
Below the weekly briefs, each brief has a card:
- ACTIVE or PAUSED, and EVENT for a brief that runs when data changes;
- who it is for (For: {name}), and what it reads, for example Reads: all connections;
- FREQUENCY, NEXT RUN and LAST RUN. A brief that has not run yet says Never run, not a success or a failure;
- how it notifies (Notify: {channels} · {condition}, or Notify: off), and under LAST NOTICE what its last notice did: Sent, Not needed, Not sent (with the reason), Partly sent or Waiting for the run to finish.
The switch (Turn brief on or off) pauses or resumes a brief. Edit brief opens it in the editor. Delete brief asks Delete brief? first. Filter Tasks shows All, Active only or Paused only; a filter nothing matches says No briefs match this filter. CREATE NEW SCHEDULE opens a blank editor.
With no brief at all, the page says No briefs yet and offers Create brief. A list that could not be read shows the error, not an empty page.
Create or edit a brief
The editor is titled New brief or Edit brief: A question FACE asks on its own, for one person, and who hears the answer.
Who it’s for
Pick the persona, or Generalist view. Their question fills in below.
What to ask
Type the question in plain words, or pick one under Start from a common question. The question is also the brief’s name.
Where to look
Tick the connections each run reads. With all ticked, it reads every connection, including ones added later. A brief that reads nothing cannot be saved.
Who hears about it
Pick WhatsApp, Phone call or Email, and when to Tell them: After every run, When it drafts a Twins decision, When a decision needs approval, or When $ at stake reaches a threshold with a Minimum $ at stake. Only decisions that state a dollar figure count toward the threshold.
When a run finishes, FACE tells the numbers in Settings › Integrations › Channels what needs a decision: the new decisions, the top ones with the money at stake and the deadline when stated, and a link to Actionable Twins. Email goes out from the mailbox connected under Settings › Integrations › Channels, to that same address. With no mailbox connected, the editor says email is off.
When
At a set time runs Every day, Every week or Every month, at the time of day you save it. When data changes runs on events (see below). Times are on this device’s clock.
Save brief
Next run shows when it will run first. Cost reads Not estimated: FACE does not forecast what a brief that has never run will use. Select Save brief. Brief saved. confirms it; Could not save the brief. Nothing was changed. means nothing was stored.
At a set time, or when data changes
A brief set to When data changes runs when a connection’s data listener sees the changes you ask for. The run is the same full run as a timed one.
- Listen to: a PostgreSQL connection with the change-event ledger installed, or a Kafka connection. No other source type has a data listener.
- Run after this many events: how many matching events start a run.
- Wait for more events (seconds): after the first matching event, wait this long so a burst of changes becomes one run.
- At most one run every (minutes): the cooldown between runs.
- Only tables or topics starting with and Only this change narrow what counts.
Saving turns the connection’s listener on, on the managed runner. Its events and listening time are metered to your account. NEXT RUN reads On the next matching event. A brief never runs while its previous run is still going, and events that arrive while it is paused are not counted. Pausing or deleting the last active event brief on a connection turns its listener off.
On an event brief’s card, LAST TRIGGER says when it last fired, how many events fired it, the first of them, how many of their rows were read back, and the run’s outcome. When the run’s analysis finishes, RULE RESULTS FROM THESE CHANGES lists each rule the changed rows bear on, with its verdict. Not fired yet — waiting for events means no run has started.
Data listeners
When any connection’s listener is on, DATA LISTENERS lists it: LISTENING, STARTING, DEGRADED, NOT LISTENING with the reason, or OFF; the events and bytes it read; and the account its usage is metered to. Not reported by the runner yet means the runner has said nothing yet; the page does not guess a state. The page reads the listeners again every 15 seconds while it is open.
RPCs behind this page
SchedulesService.ListSchedules,CreateSchedule,UpdateSchedule,SetScheduleActive,DeleteSchedule.SchedulesService.ListPersonas,SavePersona,DeletePersona, for the personas.
See the API reference.