Skip to main content
A piece of work is one change meant to move the answers, such as fixing a page, writing a piece or pitching a source. The API calls it an action. Heralded suggests work from what each report finds, and you can add your own. The Work page holds it all, in five groups: Needs you, Suggested, Heralded is on it, Results and Closed. One deliverable can rest on evidence from several sources, such as a topic’s problems and a site AI answers cite. Distinct content pieces on the same topic are separate actions. Heralded weighs your website findings, AI answers, sources, opinions, topic gaps and search results together to choose suggestions. Open an action to see the dated evidence behind it and, when available, why Heralded chose it. Access problems, dead pages, measured site checks and work you asked for keep their place without waiting for that choice. How engines describe your brand can be addressed through a correction to a third-party page, a rewrite of your own page, or a new piece that states a missing claim or supplies proof. An About page can be rewritten too. Heralded no longer files positioning-fix suggestions or suggestions to update every page’s positioning by hand. Existing work you have started or acted on stays in place. Work diagnosed from a lost question or a competitor’s gain keeps the question’s market and audience. A pitch from a Google keyword check keeps that keyword’s market and audience. Open the action to see its scope. Findings that ask for the same output on the same target, market and audience share one action, with their evidence combined. Your homepage’s structured-data checks share one site fix. A page update and an outreach pitch stay separate, even when they address the same question. Duplicate suggestions are withdrawn on the next weekly report. Work you have started stays in place. A pitch to a source is one action whichever topics cite it, and each topic’s finding joins its evidence. A website action keeps every affected page on its checklist until a later Website read checks it. Pages that pass are marked Fixed. Pages the read did not check keep their last known state, and newly affected pages join the action. The count shows how many pages still need the fix.

Work for ecommerce brands

For a shop, the same kinds of work apply to products, and each rests on dated evidence from the weekly report.
  • Product markup. A product page whose Product markup lacks a field the catalogue knows, such as the image or the product code, gets a site fix. Heralded writes the markup from the catalogue: a Product with its offer, or a ProductGroup when the product has variants. It never writes ratings, shipping or returns, and a missing field the catalogue holds no value for stays yours to add. You paste the snippet into the page, as no connection writes a product page.
  • Product page rewrites. A product whose price an answer states wrongly, or that never appeared where its topics were asked, can have its page rewritten to state those facts, with an FAQ and a comparison. The rewrite rests on what answers say of the product and what your page states. A price counts as wrong only when the seller shown is your own shop for the same variant and currency. Any other price is the price at another seller.
  • Sellers. The sellers AI showed for your products are exposure, and file no work. A seller shown for the products of several other brands and never for yours is an opening, with steps to get your products listed there. It is not a profile to claim.
  • Reviews and roundups. A review site, roundup or affiliate that answers cite beside product cards is pitched to review or include your products. A directory is still a listing.
Verifying actions explains how each is settled.

Assets

Choose Assets on Work to list the assets Heralded has made for your brand. Filter by Type, State or Owner. Each row opens its work item’s full page. A piece appears once it has a draft; the work pane still shows its progress before then. The list also includes short drafts, prepared site changes and llms.txt files. The API serves the same list at GET /v1/brands/{brand_id}/assets, with the list_assets MCP tool. Filters apply before paging. The action read supports a compact preview with with_details=false and paged activity, pages, targets, versions, evidence and sources sections. A compact preview carries each step’s latest five events, and section=activity with step pages one step’s events. with_viewer=true includes the names visible to your caller on those events, the fix kit and the remaining free redrafts. On an email task it adds the senders your caller may choose in sender_choices, the suggested one in sender_suggestion, sender_gap while a sender is owed, whether your caller may approve from the stored sender in approvable, and that mailbox owner’s sender_owner_first_name and sender_owner_account_id.

While your team works

Before a result is ready, its section names the agent working on it, with progress and an expected time when available. A new report keeps your previous result visible with Updating and its date. Partial marks an incomplete result. A failed update keeps your last good result and says Last update failed. Pages and open panes update as results arrive. Work of the same kind by the same agent in one report shares a row, with a completed count. A row stays Working while any of its work is running. Once none is running, a failure marks the row Failed and shows how many failed. A report that has been delivered is Done, even when one of its steps could not add its part. When a weekly report or daily update fails and a later one finishes, the failure leaves the activity lists and stays in that run’s history in its pane. Home shows your next decisions and current work. On Work, work in progress sits under Heralded is on it. Work that needs your decision belongs in Needs you. Finished work belongs in Results. Failed background operations stay out of these lists; a failed update keeps the last good result on its page.

What every action carries

Heralded suggests an action only when it is work Heralded can deliver. A result to hope for, such as engines describing your audience differently or winning back a lost question, stays a finding. A lost question or a competitor’s gain files the work its likely cause points to. A suggestion carries:
  • an act on a named target, such as a page, a topic or a site;
  • its grounds, with the dated evidence behind them;
  • what it aims at, with its expected gain;
  • its steps, each done by Heralded or by you;
  • when it is done;
  • a deliverable Heralded produces: a fix, a draft, a piece or a checklist.
It also names what Heralded tracks once the work is live. That never holds a suggestion back. Work you ask for is filed as You asked. Work you add with Work on this, such as from a Website finding or a page that contradicts you, keeps that insight as its evidence. So do correction requests, page fixes, manual pitches, topic orders and chat proposals. Piece orders, page-rewrite orders, Write this and opinions you answer need no evidence. Suggested listings use Category data, based on where AI answers cite review sites and directories. Every task leads with one observation and its date when evidence is available. Evidence shows the other dated observations behind it. A newer observation of the same measure replaces the older one; independent evidence keeps its own date. Work you have started keeps its instructions. On each weekly report, Heralded withdraws the untouched suggestions that no longer carry all of this, with an event under its steps saying why. A suggestion is untouched while nobody has acted on it. Restoring one counts as acting on it. Work you have started keeps its job. A withdrawn suggestion comes back when a later report finds the work again with its evidence. Heralded also withdraws an untouched suggestion when none of its cited evidence remains in a completed check, or when another opportunity is worth pursuing instead. Its timeline records the reason. A suggestion without cited evidence waits for a completed check of that kind of work. An incomplete check or a failed weekly review takes nothing back. Work you requested, restored, edited or started stays in place.

Expected gain and ranking

Each suggestion carries an expected gain: high, medium or low. It comes from the kind of work. Letting AI engines and search fetch and read your site is high. So is a comparison page against a competitor that leads your comparison questions, or whose own pages engines cite there, as Likely causes describes. Pitches, listings and a new page for a buyer need are medium. Structured data, title and description updates and other site hygiene are low. Work you asked for has no estimate. Heralded no longer estimates score points before work is done. It shows the measured gain once the work is verified. Heralded ranks suggestions by how much of your search demand the work can reach, counted in monthly searches for questions and in monthly Search Console clicks for pages, its expected gain, how sure Heralded is that the work applies and how much is left for you to do. Severity does not rank work, and neither does how easy the result is to measure. A best-practice fix whose effect no report can measure ranks on its expected gain, as if it reached one typical question. The overview, shell and Work summary serve one set of counts. Work counts exclude setup, dismissed work and withdrawn suggestions. A completed report keeps report.actions_found from when its counters finished. The rail badge equals counts.your_turn, using the assignee scope for the person reading. open_action_count is a deprecated alias of counts.open. Select a piece of work anywhere in the Command Center to open its work panel on the page you are reading. The address names the open work and keeps your page filters. Closing the panel returns to that page.

Work on this

What Heralded finds shows Work on this where a kind of work fits it:
  • a finding on Website, in Fix first, Findings and the finding’s pane;
  • a finding or a check your page falls short on, in the page’s pane;
  • a page that contradicts one of your claims or facts, in the claim’s pane;
  • a site in Worth pursuing on Sources;
  • a topic whose buyer questions no page of yours answers, in the topic’s pane, for its market and audience;
  • a question an engine’s latest answer leaves you out of, in the Questions table and in the question’s pane;
  • a competitor’s website move under Changes this week on Website › Competitors, when Heralded would suggest a comparison page against them.
  • one of your own products, in its pane on Products, when its weekly evidence offers a page rewrite, product markup or a retailer to be listed with.
Rows where no kind of work fits show nothing. Work on this lists the kinds of work that fit, each named as it would be filed, with what starting it spends: free or its content credits. Adding it spends nothing. Something else opens the Herald with what you are looking at attached, so you can describe the work you want. Choose a kind and Add to Work. The work is filed as You asked under Suggested. Once work is filed, the row shows its stage instead: Needs you, Heralded is on it, Waiting on others, Scheduled, Live or Dismissed. A topic’s panel names its work’s stage as Work does, such as Your review for a draft waiting on you. Select the stage to open the work’s pane. Adding the same work again, or work another row already led to, returns the work you have. In Fix first and Findings on Website, the Questions table, Worth pursuing and a competitor’s moves, tick rows to add several at once. The bar at the foot of the list shows how many you selected, with Add N to Work and Clear. Each row is filed with the first kind of work that fits it. A message then says how many were added and how many were already there, and names each one Heralded refused, with the reason. Viewers see the stage of work already filed, but not Work on this.

Needs you

Work opens with a line of figures: how much work needs you, how much Heralded is on, counting work waiting for a reply, how much is live, and how much is done this quarter. Then comes the box of what is yours to decide. Its title counts the work waiting on you, such as 3 to decide, and the same count is on Work in the rail. The line under it says what that work is, such as 1 draft to review, 1 fix to approve and 1 other step for you. Start walks every decision in the box, oldest ask first, on each one’s full work page. Start on Home walks the same decisions in the same order. Home holds your fixed weekly decisions. The box lists your decisions and steps, oldest waiting first, five per page. It holds your own work, unassigned work and work assigned to someone who left the team or cannot start work. When a teammate who can start work owns an ask, it counts in their Needs you, not yours. A member who cannot start work sees the same rows without buttons, and the rail badge reads Work waiting on your team. Each row shows the kind of work, its stage in words with a bar of its steps, the focus it serves and how long it has waited. The focus is a starred topic or competitor. A suggestion says Outside your focus when it serves neither and you have starred a topic or competitor. Select the row to open its work panel. A row has a button only for a step that needs no panel: Mark as posted, They replied, No longer waiting and Confirm fix. An email to review shows Review, and a reply to answer shows Respond, each opening the task’s emails. Each of these offers Undo in its message where the step can be taken back. A stopped site check links to the place you can resolve it. A failed first draft returned to you appears here with its next step. When two or more decisions wait on you, the bar at the foot of the page offers Review N, which walks the same decisions as Start. It has its own keyboard shortcuts. Opening a review applies no change and sends no email. When there is nothing to do, the box says Nothing needs you right now.

Suggested

Suggested opens by default. Select its heading to collapse it. Suggestions appear as cards in Heralded’s order, one row at a time, with a pager for the next set. Each card names the work, its kind and the focus it serves. On a phone, you see one card per page. Work you put off with Later waits under Later in the same group until its day. Tick rows to act on several at once. The bar at the foot of the page shows how many you selected, with Clear, Not now and Start N. Start N names the content credits starting them spends, such as Start 2 · 1 credit, and opens a confirmation that lists what each one starts and whether its draft waits for your approval. Not now asks why, with one tap:
  • Later puts the work away until Next week, In a month or a day you pick. It then returns to Suggested, and nothing starts it.
  • Already done dismisses it.
  • Not relevant dismisses it, and Heralded stops suggesting that kind of work for that target.
  • Too much work dismisses it.
Work you set aside moves to Closed. Restore in its pane, where offered, puts it back with its draft. Undo on the dismissal message does the same. Restoring work marked Not relevant lets Heralded suggest that work for its target again. An unplaced content order returns as suggested and spends a credit again if you start it again. During a trial, Heralded shows up to six untouched suggestions at once. Held-back suggestions appear at the foot of Suggested as N more suggestions on the full plan. Members who can manage billing also see Upgrade now. Starting, dismissing or deferring a suggestion frees a place. Placing a suggestion, changing its write language or editing its draft keeps its place. Work you asked for and setup items do not use these places. When there are no suggestions, the group says Nothing suggested right now.

Heralded is on it

Heralded is on it lists work Heralded is doing now, with its own recurring jobs, such as the weekly report or a site check, and how far each has got. A job that failed and that Heralded will try again stays here, marked Failed, with when it tries again; one only you can fix moves to Needs you. Heralded’s next scheduled jobs follow as the group’s next lines. Work waiting on someone outside your team follows under Waiting for a reply. Each row reads its stage in words, such as Writing the draft. When nothing is running, the group says Nothing running right now.

Results

Results lists delivered work, five per page, with its label beside the title: Paying off, Cited or Delivered, in that order, newest result first within each label. Each row shows its kind, the day it went live and the steps it has reached. A piece of work shows only the steps its kind tracks, such as Live, Read by AI crawlers, Ranked on Google, Cited and the measured outcome. A reached step has a check. A step not reached yet reads not yet, and one Heralded cannot see reads not connected or couldn’t check. The measured outcome reads Recommended more, Mentioned more, No effect, Fell, Inconclusive or Too early to tell. Home brings results into your week timeline. A first citation names the engine and date even if a later measurement finds no move or cannot measure the work. Pending work shows result by and its due date, such as Cited · result by 17 Nov. A citation records what an engine did; it does not claim the work caused a gain. Verifying actions explains the outcomes. When nothing has finished, the group says Nothing finished yet.

Closed

Closed lists every task that ended without a result, newest first, five per page. Each row shows its kind, the day it closed and how it ended, once: Stopped, No reply, No reply recorded, Declined or Opted out for work that had started, and Not now, Not relevant, Too much work or Already done for a suggestion you set aside. Closed work counts in no figure on Work and never in Results. Its pane offers Restore where the work can be restored. The group is hidden while nothing has closed.

One subject

Work can be filtered to one question, topic, keyword, figure, source or competitor, with subject=<kind>:<id> in its address, such as ?subject=prompt:<uid>. A chip names the subject, and Clear returns the page to all your work. Needs you, Suggested and Heralded is on it list only the live work about the subject, in their usual order, and their counts follow them. A subject your brand does not have lists nothing, and its chip still offers Clear. Results is not part of a filtered page, because a subject’s work is the live work. Links to the old Actions page, such as /actions, /actions?focus=<id> and /actions/<id>, open Work or the work’s panel.

New

New in the Work header orders work from you. It offers:
  • Write something new: an article, guide or comparison page on a subject you give. It uses one content credit. Name it, say what it should cover, and choose its format and language.
  • Improve a page you have: paste the address of a page on your site. Rewrite the first screen drafts its headline, subheading and call to action for free. Rewrite the whole page uses one content credit. The address must stay on your site after any redirects. Asking again for the same page returns the work you already have.
  • Ask a site to correct how it describes you: choose one of your facts that pages elsewhere contradict, then the page. Heralded drafts the request to its editor, at no cost. A page already in Work shows its stage instead.
  • Describe it to the Herald: write what you want, and the Herald proposes the work that fits.
The dialog shows how many content credits your brand has left. Viewers do not see New.

Heralded’s work

Heralded writes pieces, prepares outreach and works on site fixes. It also runs its own recurring jobs, such as the daily update, the weekly report, the site check and the brand-mention check. Their panels are read-only, with Copy link in the header. Ask the Herald opens from the rail. The Herald answers questions about every kind of work in one conversation.

Kinds of work

Outreach waits within each route’s Up to N a week limit in Automation. Content ideas and page rewrites suggested from a topic’s content verdict count toward your plan’s ready-idea allowance even while held back. Rewrites suggested from Search Console do not. Starting or putting away an idea frees a place for the next suggestion. A topic can have several ideas for different buyer questions, even when it already has a page. Each idea names the question or keyword it addresses. A question idea covers every engine where Heralded measured that question as a problem. On a paid plan, other suggestions have no waiting limit, and Suggested ranks them. A trial’s shown-suggestion limit covers every kind of suggestion. Work you have started or restored stays. Site-wide website suggestions and website rewrites you have not touched are withdrawn when a report measures their finding passing. Other suggestions can stay in Ready to start, marked Not in the latest weekly report, until you start them or choose Not now.

Best-practice work

Heralded also suggests work that no loss prompted, because a known good practice is missing. Each shows its grounds. Work based on published guidance names that guidance and the date Heralded last checked it:
  • Let AI crawlers read your pages. A page that matters carries noindex, nosnippet or max-snippet:0, sends almost no text in its HTML, or sits behind a robots.txt rule that refuses a citation crawler on its path. A page matters when it is your main site’s homepage, is cited in your reports, matches a topic you track, has Search Console clicks, or is a pricing, product, solution or comparison page. One action covers every affected page with the same finding. Its checklist gives the fix and then lists all those pages. Robots.txt refusals share one site fix.
  • Write a comparison page against a competitor. A competitor you track is the pick on at least two of your comparison questions and on more of them than you, and none of your comparison pages names it. Its grounds are category data.
  • Get listed on a review site. Engines cite a review site in your category, and Heralded has not found a profile of yours on it and you have not given one under Review profiles in your brand settings. Its grounds are category data.
  • Write a page for a buyer need. No page of yours answers a topic you track. Needs that serve one tracked topic share one action, even when the questions change between weekly reports. Its title and writing instructions keep the questions. The next report folds untouched duplicates’ evidence into one action, keeping work you have started or restored. Started work keeps its title, writing instructions and state.
  • Complete your Organization structured data. The homepage carries the company’s name, URL, logo and two sameAs profile links. It is part of the homepage structured-data site fix.
Heralded recommends nothing written only to appeal to AI systems. It files no action for an llms.txt file or for lengthening a page or adding a list to it. Whether AI training crawlers may read your site is your choice, so no action asks you to allow them. Title and meta-description findings also share one action per finding across every affected page. These batches carry a checklist, without a draft. A website rewrite updates one chosen page. Message, first-screen and positioning findings can call for a homepage rewrite; rewrites for a tracked topic’s content verdict keep their own page-eligibility rules. Buyer needs worth tracking appear as suggested topics in the Suggested view of Topics. Choose Track there to track one. Not every finding becomes an action. A competitor newly named in your answers is announced under Changes on Home, as Competitors describes, and files no action.

Likely causes

A question you lose, or a competitor gaining share, does not become an action by itself. Heralded looks for its likely cause in the answers and the pages they cite, and suggests the work that cause points to. The rules are fixed. A fact Heralded does not hold, such as a page it never read, is never treated as evidence, so a loss with no evidence for a cause gets no action. A lost question counts once the loss has held for three daily updates or weekly reports in a row, after at least three that named you, or cited your pages for a lost citation. Heralded then checks four causes: The page-change cause needs a stored version from before the loss and a current version. If Heralded has no earlier version, or the citation and change fall on the same scrape boundary, it keeps watching without naming a cause. When one page is cited in every answer since the loss, the piece names it as the page to learn from. A content gap whose page would answer several questions covers a loss on any of them. For a competitor that gained share of voice in a weekly report, Heralded checks two causes in that report’s answers: Causes that call for the same work share one action, which lists every cause. A cause for work already open joins that action. Different work stays in separate actions, each linked to the loss or the gain. Outreach follows the rules in Outreach, so a site you muted gets none. Changes on Home ends the line for a held loss or a competitor’s gain with what Heralded found: the likely cause and how many actions it filed, or No clear cause yet; Heralded is watching it. A loss still watched is checked again on each daily update and weekly report while it holds, and a competitor’s gain on each weekly report. Either gets its action once a report brings the evidence.

Work from search and crawler signals

Five signals Heralded already collects file work on each weekly report. The action carries the figures and the dates they cover. A page is losing clicks when its latest 28 days drew at most 70% of the clicks in the previous weekly report’s 28 days, and that report counted at least 20. A page is just outside the first page when it averaged a position between 10 and 20 over at least 100 impressions in the 28 days. Both need a live page in your site inventory. A report in which Search Console did not answer files nothing, and a page the report did not list is not read as recovered. A dead page needs Cloudflare, the source that verifies a crawler. It qualifies after three fetches in the 28 days. The action carries the steps: send the address to the live page that answers the same question with a permanent 301 redirect, or restore the page. You make that change yourself, because no connection writes a redirect. A pitch from Google comes from the week’s keyword checks. It names a third-party page in the top 10 that Heralded read and found does not name you. It files only for a site that takes a pitch, so review sites and forums keep their own routes. It counts toward the Get cited route’s limit and ranks after the sites AI cites. An opinion can suggest a piece when it is active, negative and about your brand, as Reputation describes. Heralded suggests at most one standalone objection piece for the brand each week. Other objections become angles on topic pieces. After a weekly report checks opinions, untouched standalone suggestions it does not suggest again are withdrawn. The piece costs a content credit when you start it. An opinion you or a teammate already proposed an answer for, or put away, files nothing. Heralded asks no site to correct an opinion, because an unwelcome view is not an error. When a report no longer finds the gap, an untouched suggestion stays in Suggested, marked Not in the latest weekly report. Started work stays in place.

Action metadata in the API

The action read’s meta.surfaces["actions.work"] dates the current short draft. During a redraft, updating is true and as_of keeps that version’s creation time. If the redraft fails, last_attempt_failed is true and the current version remains available. A replacement version clears the failed flag and carries its own date. The app, REST GET /v1/actions/{action_id} and MCP get_action use the same metadata.

Results in the API

GET /v1/brands/{brand_id}/results and MCP list_results return delivered actions in rows, with counts for each result label and a total. Setup actions, question additions and deliveries undone by reopening are excluded. Each row carries status_label, delivered_at, result_at, first_citation, citation_count and measured. Paying off requires a verified gain. Otherwise a qualifying citation gives Cited, and uncited work stays Delivered, including work measured with no gain or that could not be measured. measured is the same measured outcome served on the action. It carries state, summary, reason and at. While pending, at is the result due date when one is known. A citation stays available whatever the measured state. Set order=label, the default, for Paying off, then Cited, then Delivered, each newest result first. Set order=newest for newest result first across all labels. result_at is the latest delivery, first citation or measured outcome date. Use limit and the returned next_cursor with the same order to continue. Counts cover the whole result list on either order and every page. The overview’s verified_actions continues to select verified gains and citations from delivered work. It does not include work still waiting for a result.

Team conversations

The Herald answers questions and offers changes for you to confirm. Earlier conversations stay readable as history. Work updates stay on the action and in your notifications.

Evidence for work

GET /v1/brands/{brand_id}/evidence and MCP list_evidence return the evidence of your latest weekly report that holds it. Each item includes its id, module, kind, target, segment, fact, observed_at and the plays its owner offers. Member requests and completed setup items are excluded. With no report evidence, scan_id and run_number are null and items is empty.

Insights and their work

An insight is something a read finds that work can address. Each of these rows carries an insight field:
  • a Website finding, on the Website read and on each page it names;
  • a check a page falls short on;
  • a page that contradicts one of your claims or facts;
  • a source worth pursuing;
  • a negative opinion of your brand;
  • a topic’s unanswered question;
  • a move on a competitor’s website;
  • a question that an engine’s latest answer leaves you out of.
insight has three parts:
  • id stays the same from report to report: finding:<id>, check:<page>:<check>, page:<claim>:<url>, source:<domain>, opinion:<id>, topic:<topic>:<segment>, move:<competitor>:<change>:<week>:<url> or question:<prompt>. Every unanswered question of one tracked topic shares its topic’s insight.
  • kinds lists the kinds of work that fit it, each with its play, the title the work is filed under and the content credits starting it spends. A finding fits its fix, a contradicting page a fix of your own page or a correction request to a third-party one, a source the outreach its route takes, a negative opinion a piece answering it, and a topic a new page when it is missing or a rewrite of its closest page when it is weak. A check a page falls short on fits a rewrite of the page when Heralded can rewrite pages of its type. A competitor’s move fits a comparison page against that competitor only when Heralded would suggest one: the competitor is the pick on your comparison questions and no page of yours compares you with it. A question you are left out of fits a piece answering it. kinds is empty when no kind of work fits.
  • work is the work already filed from it, with the action’s id and state, or null. It includes settled and dismissed work. Every failing check of one page shows that page’s rewrite, and every move of one competitor its comparison page. A question shows the topic page or page rewrite filed for it, or a piece that targets it, whoever filed it.
Information findings carry no insight, and neither does a page’s finding whose work rewrites another page. Adding work from an insight files it as You asked in Suggested, with the insight as its evidence. A move’s comparison page rests on the comparison that calls for it and on the move, and a question’s piece on the latest answers that leave you out, read when you add it. Adding work that already exists returns it instead. A held-back suggestion becomes yours, withdrawn work comes back, and work in any other state stays as it is. Two insights that lead to the same work share one action. You can add work from several insights at once, and each reports whether it was added, was already there, or was refused because it is no longer in your latest report or that kind of work no longer fits. Viewers can’t add work. Adding work happens in the app, with Work on this, and isn’t part of the v1 API.

Action fields

GET /v1/brands/{brand_id}/actions and MCP list_actions return shown actions. total counts the shown actions matching your filters; suggestions_kept counts the brand’s held-back suggestions, separately from those filters. Held-back actions stay out of lists, counts, detail reads and drafts until a place opens or billing starts. The customer API and its list_actions assistant tool include a member for each action. writer identifies content and competitor gaps, publicist identifies outreach and correction requests, and engineer identifies site fixes. These are stored work-kind keys. Heralded’s own daily updates, weekly reports, site checks, brand-mention checks and competitor searches belong to the Herald. Setup and low-quality question reviews have no member. API fields and member identifiers keep their existing names, including analyst and analyst_week. placed_position is the action’s position in the brand’s proposed order, with 1 first. It is null for actions nobody placed and clears when the action leaves Proposed. Proposed actions come as this week’s work and then the backlog, each in this shared order followed by Heralded’s ranking, as Suggested describes. A scheduled action’s group is scheduled, and scheduled_for holds its start date. Scheduled work appears under Later in Suggested. Every action in a list or a detail read carries ending and wait. ending says how a task ended: its key, the words Closed shows in label, and at. Its key is no_reply, no_reply_recorded, declined, opted_out or stopped for work that had started, or not_now, too_much_work, not_relevant or already_done for a suggestion set aside. It is null while the action is open, and outcome keeps its meaning. wait says what an open task waits for: kind is answer to an email of yours, agreed on a date they gave, queued behind another task to the same contact, asked whether they replied, or blocked on someone you named; on names who; due_on and due_source, given, default or ours, say until when and where that date came from; acts says whether heralded or the member acts then; and since says when the wait began. It is null while the task waits on nobody. job.endings lists the ways you may end the task in its current state, each with its key, label, the verb it sends and an optional confirm. A close verb closes the task’s emails with the key as the reason, and skip lets the follow-up due after a missed date go unsent. New verbs can appear: offer one you don’t know nowhere. An ending that answers the task’s wait comes first. The actions list in the API and MCP list_actions accept assignee=me for actions assigned to you, or assignee=heralded for actions with no person assigned. Omit assignee to include anyone. The filter applies before pagination, and total counts the matching actions. The actions list and MCP list_actions accept subject for the live actions about one question, topic, keyword, figure, source or competitor: prompt:<uid>, topic:<id>, keyword:<id>, figure:<axis>, source:<domain> or competitor:<key>. They match the subject’s actions_total, subject to the topic’s selected period. subject_label names the subject. For a subject your brand does not have, nothing matches and subject_label is null. One question, topic and keyword, each axis pane, one source and a competitor page list their live actions highest priority first. actions_total counts all of them before the list is cut. next_step_action_id and next_step name the highest-priority one that waits on you and that you can act on, even when it ranks below the listed ones. They are null when nothing waits on you or your role cannot start work. Use assignee=mine_or_open with group=your_input for the Needs-you list. If you can start work, it includes your actions, unassigned work and work assigned to someone who left or cannot start work. Asks owned by a teammate who can start work appear under group=waiting, with holder=waiting and demand naming who they wait on. Readers without permission to start work and service tokens see every ask in your_input. A failed first draft handed back to its owner and a stopped site check appear here too. waiting_since dates when the current ask began, and the Needs-you list puts the oldest ask first. A stopped site check has no action button; its route points to Content. Omitting assignee keeps the existing list and order. Action timestamps describe separate moments:
  • started_at is the first time Heralded starts the action. Revisions and retries keep that first start.
  • delivered_at is when the result goes live, is sent or is published.
  • paid_off_at is when verification credits a positive measured gain. Delivery alone does not prove a gain.
Dismissed actions have none of these timestamps. Missing evidence leaves a timestamp null. Setup items do not count as team actions and have no lifecycle timestamps. While an action waits on you, preview carries up to 400 characters from the draft’s opening lines, an email’s recipient and subject, or the planned change. A preview is plain text and can include markup. Open the action to review the full result. Each action also includes a note with what’s happening, why it matters, what Heralded can do, what you need to do next and how the result is checked. Its short_form names the deliverable in one neutral sentence. whats_happening states the same observation as grounds.cause, and grounds.observed_at dates it. why_it_matters is the reason in grounds.why, and null when the work states none. A source task’s finding, evidence and note refresh with each new observation. Other actions change their title, reason, evidence and note when a weekly report changes what it suggests: a figure moves to another range, a competitor is named or dropped, or new evidence appears. Each observation keeps the date its figures were measured. Figures come from the action’s facts, and an invalid generated note uses a template. what_i_need_from_you asks you to start a proposal or take the current review or approval step. It says there’s nothing to do yet while Heralded works or waits for a result. What Heralded can do reflects your current site connection. A content action’s detail dates its question or keyword figure to the newest weekly report Heralded used when filing it. Suggested actions refresh their detail from the merged grounds. Started actions keep their stored instructions. grounds says what an action rests on. Its kind is your_data, category_data, best_practice or you_asked. cause states the leading observation and grounds.observed_at dates it. A stored cause with a date leads as it stands. Otherwise the newest evidence observation leads with its own date. The finding leads only when there is no evidence, and stays undated. An undated likely cause appears at the start of why as “Likely cause: …”. Work without evidence or a dated cause stays undated. cause can be null on work you asked for with no finding or evidence behind it. evidence lists the dated observations behind the action, besides the one cause states, each with observed_at and fact. Observations from evidence modules also carry a stable id, which stays the same when their figures change. It is null on older observations. Optional measure identifies an observation that a newer reading replaces. Optional url links to a cited page. Independent evidence keeps its own observation dates. why gives the reason behind newly filed work, from its observations or your request. It can be null on older work until its next refresh. A best-practice action lists the guidance it rests on in guidance, each with its publisher, title, url and checked_on date. grounds is null on an action filed before actions carried their grounds, until a weekly report refreshes it. done_when says when the work is done. For outreach, it follows the goal: a page on the site names you for a pitch or a rates request, a correction is done when the page no longer says it, co-marketing when you confirm it is live, a community reply when you posted it, and a listing when your profile is live. tracking names the signals Heralded tracks for this kind of work once it is live: live, crawled, ranked, search_console, cited and moved. grounds.targets lists the question or keyword results the work targets. Each has kind, its stable uid, engine, metric and language. Language comes from the measured result and is null on targets stored without it. A question target names its engine and uses recommended; a keyword target uses rank and has a null engine. Work with grounds but no explicit targets carries an empty list. Actions predating structured grounds keep grounds: null. Targets are kept with the result when you mark the action done. A piece’s question targets are measured on Recommended, using only each target’s engine. The untouched questions used for comparison use those engines too. Keyword targets appear in the page’s Google ranking trail, even if you stop tracking them. They do not count toward the question verification. Work without explicit targets keeps its Mentioned measurement and uses your active keywords for the ranking trail. The verification windows and evidence requirements still apply. gain is the expected gain. Its band is high, medium or low, and null on work you asked for. aims_at says what the work aims at. expected_impact_pts is always null. credits_spent is the content credits charged to this action and not refunded. A refunded failed start reads 0; credit_cost remains the cost of dispatching the work now. An action’s evidence lists its linked questions, the answers that name you and the total answers in the latest report, including daily answers pooled into it. Failed calls do not count. Each question has an Answers link, and the action has one link to the combined answers. A question with no answers has zero counts. Work with no linked questions has an empty list and no combined link. GET /v1/actions/{action_id} and MCP get_action add what the action’s pane shows: its state, the verbs it offers, its job and costs, verified impact, demand, schedule, assignee, steps, current step and shared thread events. Each entry in steps carries its events, oldest first, and event_count. An event belongs to the step whose kind of work it records, such as a draft to the step that writes it. An event no step records sits under the step last finished when it happened, or under the first step, so every event shows under exactly one step. kind_tag is a tag on the kind of work, shown beside its state, and null on work that has none. The verb the app calls Start is dispatch in the API. When a piece Heralded was writing fails, job.failure gives the reason and job.stopped_at names the step it reached. dismissal_reason says why a member put the action away: not_now, too_much_work, not_relevant or already_done. It is null when no reason was given and once the action is restored. Each step carries its status: done, now, ahead, or ended for the step an ended task had reached; and its lane, main or article for the article an outreach agreement needs, which runs beside the emails. Each event carries its line, who did what in words with dates in words and no version numbers, and tone, failure for an event that failed and null otherwise. summary is the same line for no reader in particular, with a teammate where line says “You”. Draft events distinguish the first draft of an email, reply or follow-up from a redraft of that same email. Identical draft events under a step fold into one entry with a count. Heralded’s start appears once each time the task is opened. A reply that asks for an answer reads as Heralded starting the reply, never as a second start. Offer events name your decision and price; their terms stay on the offer. A decision whose answer never went before their next offer reads as drafted, not sent. drafts lists the short-draft versions, each with the email it is for: null for the first email or any other draft, reminder_1 or reminder_2. The current version and the newest of each email still to go open with a greeting for today’s contact; every other version reads as it was stored. Each draft’s gaps lists what it still needs from you, in order, each with its index, its label, its kind, its request_id and its target. kind says what filling it takes: answer for an answer you write, fact for a fact you supply in its sentence, choose for your choice on their offer, signature for your brand’s email signature or opt_out for the opt-out sentence. request_id names the obligation in state.obligations it answers, or is null. target is draft for the draft’s own text, or signature for your brand’s email signature. current_draft_version names the one the action shows and recipient who an outreach email is addressed to: the person or the site’s team, the address the email goes to, its role (editorial or commercial), where it was found (address_found_in and address_page_url) and whether it is a generic mailbox the site keeps for a role. address is null until one is found or you add it. On a pitch, co-marketing proposal or correction request, correspondence carries the emails with the source: turn is theirs while the task waits on the source, yours while it waits on you and closed once it settled; waiting_for and due_on say what it waits for and until when; approved maps each email approved to go to its draft version; gaps lists what the next email still needs from you; closed names how it ended; and emails lists the emails oldest first, each with its direction, occurred_at, subject, text, sender, recipients and attachments. Each attachment has its filename in name and its byte count in size. Open files in your own mail; Heralded keeps no file bytes. On a reply, reading says what Heralded read in it: its state (pending, read or unread), said, how they answered, whether it was automatic, an opt_out, agreed or asks_payment, and its requests, commitment, away_until, contact and published_url. next_email is answer when the next email answers theirs. goal is named, correction or co_marketing. offers lists every version of the terms on the table, each with its priced options, labelling, conditions, who made it, its state, your decision, told_at and told_email_id, when an email of ours told them your decision and which one, and, while open, the ways to answer it. requests lists what they asked that is still open and yours to do now, and awaiting what they agreed to do and by when. state.recipient.proposed is another person they said to write to, until Heralded writes to them. An open offer whose agreement needs an article from you has needs_article true and states the article_credits Heralded writing it costs. Once you agree, article says who writes it (by), where it stands (stage: member, writing, review, approved, failed or sent), its content action and piece, what they asked of it and by when, the version that last went and when they asked for changes. next_email is article while the article is the email due, and the email it went in has email article. published_check says what Heralded’s read of published_url found. Read section=emails to page through them. On a pitch, co-marketing proposal, rates request or correction request, correspondence carries the emails with the source: turn is theirs while the task waits on the source, yours while it waits on you and closed once it settled; waiting_for and due_on say what it waits for and until when; approved maps each email approved to go to its draft version; gaps lists what the next email still needs from you; closed names how it ended; and emails lists the emails oldest first, each with its direction, occurred_at, subject, text, sender, recipients and attachments. Each attachment has its filename in name and its byte count in size. Open files in your own mail; Heralded keeps no file bytes. Read section=emails to page through them. mailbox names the brand’s mailbox the email goes out through, whether it is connected, who can reconnect it, the emails it sends a day in daily_limit and the email on its way, with the email and version it carries and the from_address it goes from; it is null when the email goes from your own mail. Its sends_as lists the account’s verified From addresses and default_from names its default. Each draft’s from_address stores its choice, with an empty string for your own mail and null to keep an existing draft’s sending path. state says where the emails stand, so you work none of it out: whose_move is us or them; next_email is the email due next, what it is for (purpose: pitch, follow_up, answer, hold, decision, covering, chase or introduction), whether it opens its own thread (first), whether it is approved, who sends it, heralded or member, at, when Heralded sends it, held, why it can’t go yet: mailbox_disconnected, gap_unfilled or address_required, and gaps, how many gaps you still fill before it can go, in it and in the follow-ups it covers, with your signature counted once; wait is the action’s wait; step is the key of the step in job.stages it stands at; missed names a date that passed with a follow-up to review or skip; recipient is the address the next email goes to, where it was found, the address your brand may no longer write to in refused, with its reason, its date on and a message, whether you can change it, the person they said to write to instead in proposed, and in written whether an email of ours has gone to the recipient; and obligations lists what each side owes, each with its party, kind, what, due_on, status, whether it is actionable now and, while it waits on another, waits_on in words. application adds the planned change’s state, the value it was planned against and its effect. insight_links lists the weekly reports that raised or reprioritised the action. content_piece carries a long-form piece’s stage, current full draft, fields, destination_hosts, constraints and words. The destination hosts name the sites where the piece can be published. constraints is what the order asked of the piece: the length in words as a min and max, the number of links and the deadline. words counts the words in the current draft. Pieces without a saved destination use your brand’s owned sites. Each field has its name, label and value, such as a title, summary or search description. checklist lists the steps you follow where Heralded drafts and applies nothing: a website finding’s fix, a site check’s steps or a listing’s steps. pages lists affected page URLs separately. Title and meta-description batches carry these steps without a draft. It is empty on other work. trail lists what happened since the action was delivered, one entry per signal in tracking and then the measured result, each with its state, summary, reason and at. It is empty until the action is delivered. What happened since explains each signal and state. as_of pins the evidence to a weekly report; the action itself is always current. These reads exclude per-person read markers and unread state. Action detail also serves results, with confirmed observations, targeted-question mentions, signals still being watched, failed reads, a connection offer and the measured outcome. Its ordered steps follows this kind’s tracking signals and retains pending, unchanged, unavailable and inconclusive states. Results list rows and MCP list_results carry the same object. Work results defines each step field and measured outcome state. first_citation identifies the first qualifying citation after this publication. It carries the engine id and display name, question text, stable question id, answer id and observation date. Work rows, /v1 action lists and MCP list_actions carry first_citation and citation_count. The overview’s verified_actions and MCP get_brand_overview include cited pages with the same fields. The Studio piece read and content_piece carry the same citation. Older observations can have no answer id, so they offer no answer link. citations lists up to five distinct engine and question pairs within the measurement window; citation_count counts all pairs. Citation results explains what qualifies. The flat trail remains available with its existing states. GET /v1/brands/{brand_id}/work and MCP get_work serve current agent jobs, the next scan, completed work in the last seven days and since the brand started, and the Herald’s week. Each job names the action get_action reads in action_id and action_kind, who holds it in holder, a running scan’s progress and its current_step. Answer and page tallies include daily updates. since_started counts the answers list_answers returns without period, and week those whose run finished in the last seven days, which its read_since selects. The Herald’s week counts shown actions proposed in the past seven days, excluding held-back suggestions. It matches the Actions team. competitors_tracked counts competitors tracked now; competitors_checked_7d counts distinct competitors checked in seven days. competitors_watched is a deprecated alias of competitors_checked_7d. The operations list includes your brand’s background work, including report preparation, site and page reads, keyword research, question reads and connection checks. It excludes conversation replies, which stay with the person who asked. Completed operations remain available for up to 14 days. A weekly report stays working while its actions and findings are being prepared after its scores arrive. Once delivered it is done, and a step that could not add its part shows failed in stages. An action waiting for its next attempt stays working. A future report date appears in next_scan_at. For a reader who can start work, an ask owned by another teammate who can start work is waiting, with label naming them, such as Waiting on Florin. The owner’s own asks, unassigned asks and asks owned by someone who left or cannot start work stay needs_you. Readers who cannot start work see every ask as needs_you. Work waiting on someone outside your team is waiting for everyone. failure is site_unreachable, provider_unavailable, timed_out, access_revoked or no_result. It is null unless the operation is failed. An unrecognised failure is no_result; raw errors and provider responses are never returned. Clients should show a generic failure sentence for an unknown cause. Connection syncs, checks and crawler pulls carry subject.binding_id for the brand connection they concern. Other subject references remain available where they apply. A binding reference is null when the operation concerns no connection.

Moving work along

Open a piece of work to see its pane. The header shows its kind and state, then its title and one row of owner, expected gain, cost and focus. The owner picker stays visible. The sections show what Heralded found, the work or asset, Steps, Why and its targets. Before you start the work, Steps is the plan. Once it starts, each step lists what happened at it, with dates: the pane shows the latest three under the current step, and the full page every step’s. Each event says who did what, such as Heralded drafted the email or You approved the draft, with dates in words. Only an event that failed, such as a send or a site change that did not go through, is marked in red. Repeated drafts and checks show how many times Heralded ran them. Heralded does every step that is not yours, whatever the kind of work. A task that ended marks the step it had reached with how it ended. Evidence includes dates and links to its sources. The pane shows up to five rows per list. See all opens the full page at that section, where you can page through the rest. The work reads one title in its row, its pane and its page: the asset’s title once a draft exists, otherwise the work it proposes. A step that is yours reads Your turn. Writing you take on yourself before Heralded drafts anything has two steps, Make the change and Verify. A piece that fails stops at the step it reached, and the pane shows why above Try again. Open as a page gives the work a main column and a properties column. On a phone, the properties sit after the title. Copy link is in ⋯. Viewers can read the same work without write controls. The footer holds Ask the Herald, at most one secondary button and the one main button for the work’s next step. The ⋯ in the header holds what else you can do to the work, with Copy link last. Expand opens the work as a full page. A suggestion offers Not now, Later and I’ll do it myself. Once Heralded has started, the way out is Stop. Stop this piece asks first when the piece has spent content credits, and says how many stay spent. A saved version can be resumed in review. Stopping outreach, a draft or a fix happens at once, with Undo in its message. Close, no reply is offered only while the task waits on their answer. Assign to… appears for members who can start work when more than one person can take it, and Undo puts the previous owner back. For members who can reassign, the owner picker also offers Unassigned. When someone is removed from the workspace, loses access to the brand or deletes their account, their open work becomes Unassigned. The Asset section shows what Heralded made, with its type, title, draft, state and opening lines. A draft has one name everywhere, such as Draft 1.2: in the editor, the Asset section and Assets. Open the asset, Review and expanding the pane open the same full page. For a long piece or page rewrite, this is the asset editor. Versions, Sources and Export stay with the editor. Every work page puts its commands, such as Approve and Ask for changes, in the page header, with the close button at the end of the breadcrumb row. Its right column holds the owner, steps, evidence, targets and activity, and for a piece switches between Work and Notes. For work you do yourself, the instructions lead the main column. Old Review and Studio addresses redirect to this page. Replies and other short drafts share their Review controls with the panel, whatever their length. An email is reviewed on its task’s emails. Change the draft directly where it reads, or choose Ask for changes to send Heralded a redraft note. The line below tells you how many free redrafts remain. Fixes you take on yourself retain their completion button; Connect your site replaces it only when connecting would apply a prepared fix. Unsent draft edits and revision notes come back when you reopen the panel in the same tab, until you save, send or discard them. A short message confirms each saved change or explains a failure, with Undo for changes that can be reversed. If Work cannot refresh an open piece of work, the panel keeps the last loaded state and its address, and says Last update failed with Try again. An approval or change you saved stays saved if this refresh fails. When work lands in Needs you, such as a draft to approve, a content draft to review, a fix to confirm, a reply from a source or a reminder due, Heralded sends one “Waiting on you” email that day. It goes to the action’s owner and to members who can start work, while each recipient keeps Needs your approval on in Notifications. A draft you asked for reaches the action’s owner alone. Viewers don’t get it. Heralded drafts what it can. Nothing goes live on your site or leaves Heralded without your approval. You approve or edit each draft, or choose a step in Automation that approves a kind of work in advance. A site fix needs a connection for Heralded to apply it. With the WordPress Connector, it can apply robots.txt rules for AI crawlers and your homepage’s structured data. Without one, Heralded drafts the change and you apply it. For your homepage’s structured data, the draft is a snippet with a Copy button, which you send to your web developer. A failed connected site change offers Prepare fix again while the connection is available. It prepares a new change from the site’s current value and waits for fresh approval. The failed attempt stays in the history. Closed work offers Restore where it can be restored, and work still being verified offers Reopen.

Outreach

Heralded picks one way to reach each cited site, from what kind of site it is and how its company relates to yours: Reach out to Acme TV on YouTube names a creator. Join the conversation in r/pm names a subreddit. A site known to sell placements can also take Ask for its rates, the Sponsored placements route, beside its own: an email to the people who sell its placements asking what they charge and what it includes. It carries a Sponsored tag in Work. Heralded suggests at most one piece of outreach per site, so a site with outreach of another route gets no rates request suggested; you can still add one from the site’s pane, within the Sponsored placements limit. A rates request always waits for your approval, whatever your Outreach step. No other email raises money. A suggestion keeps the route it was filed on, and its title, also when Heralded suggests it again after withdrawing it. Starting a suggestion filed again writes a fresh email without using a free redraft. When a site’s route changes, such as when you mark its company a partner, new work takes the new route. Without an author name, an email to a person’s channel opens with a generic greeting; an email to a company or publication greets its team. A first pitch names a page from the task’s Evidence. Tasks without page evidence use the pages in the current Sources read. An email to a site shows who it is addressed to and the address it goes to under Contact, before anything is written. Heralded takes the address the cited page publishes for its author. Where that page gives none, it checks the site’s home page, contact pages and commercial page, including pages listed in its sitemap or published at common contact addresses. A rates request goes to the site’s commercial contact instead: an advertising, partnerships or sales address, or one its commercial page publishes, and otherwise the best general address. An address at the site’s own domain counts anywhere on those pages. An address at another domain, such as a publisher’s Gmail, counts where the page links it or names it as a contact, and not where it is a vendor’s or a legal one. An address like editor@ or info@ is used and labelled as the site’s own mailbox. The task labels a known editorial or commercial role and links the page it was read from. An address whose role is unknown has no role label and ranks below a general mailbox. On the API and assistant reads, correspondence.state.next_email.held is address_refused while the next address is refused or missing after a refusal. correspondence.state.recipient.candidate holds a found contact until you choose it. On the API and assistant reads, recipient.discovery gives the lookup outcome and a readable reason when an address is missing. unreadable means the site could not be read; searched_none means the search completed without an address; found means an address was found. The field is null before classification or while the task awaits a newer source read. A lookup reads at most six pages toward your monthly page reads. A completed search stands for 90 days, whether it found an address or none. If the site cannot be read, Heralded retries after 1, 3 and 7 days. A site that keeps refusing access gets one retry, without using page reads. When no address is available, Contact explains when the site blocked access, showed a bot check or a completed search found no address. Before a reason is available, it says no address was found. Add an address under Contact, or select Change beside To on the email. Your address stays over any later lookup. Changing the contact updates every unsent email’s greeting, including a greeting you edited by hand. The draft version stays the same. A contact change withdraws any approval so you review the email again. Another address given with no name is not the last person’s, so the greeting moves to the site’s team. A draft Heralded is still writing greets the new name too. Open in your mail opens with the address as the recipient. Heralded suggests a site only when AI engines cited it in at least two answers and Heralded read a page they cited. A site a likely cause names is suggested on that cause, outside the ranking. It leaves out a company that sells in your category, which includes a vendor whose cited pages name your competitors. It also leaves out app stores, marketplaces, news wires, press-release services, preprint servers and a site it could not classify. It also leaves out whole platforms such as YouTube, LinkedIn, Medium and Reddit; X, Twitter, Facebook, Instagram, TikTok, Pinterest, Threads and Twitch; link resolvers such as doi.org; analyst and consulting firms such as Gartner and McKinsey; and channels or subreddits named after your brand or a competitor you track. Get listed is for review sites and directories whose company does not sell products. Review directories such as G2 and Capterra stay as Get listed, unless Heralded has found your profile there or you gave it under Review profiles in your brand settings. Heralded ranks sites that leave your brand out by the search demand of the questions they are cited on, weighted by each site’s domain authority. When a weekly report no longer meets these rules, Heralded marks those suggestions Not in the latest weekly report. A suggestion on a target Heralded definitively refuses, such as a whole platform, resolver, competitor or vendor, is withdrawn with the reason. Work you have started or touched stays. Heralded never posts for you, and never sends an email nobody approved. Without a mailbox it drafts and you send. With your brand’s mailbox connected, Approve and send sends it from that mailbox.

The conversation’s sender

Each email goes from a mailbox and one of its addresses, or from your own mail. From on the email lists your own mailboxes under Your mailboxes, then the brand’s shared mailboxes under Shared, each address labelled Mailbox or Alias, then Your own mail. It lists only mailboxes you may send from, never another person’s personal mailbox. Until someone chooses, From shows your one personal mailbox, or the brand’s one shared mailbox when you have none. Your suggestion never replaces a sender someone else chose. With no choice and no suggestion, From reads Choose who sends, and Approve waits until you choose. Changing From saves a new version of the email and its follow-ups, which needs your approval. Approve and send sends from the mailbox and address From shows. The first email that goes fixes its mailbox and address for the conversation. Follow-ups, answers and the article’s email go from it, even if the mailbox’s default address changes, and From shows it without a choice. An email you mark as sent, when its draft names no mailbox, fixes the conversation to your own mail: From reads Your own mail until a copy of an email names your address. Taking over a task changes who it is assigned to and who drafts it, not who may send from its mailbox. Only someone who may send from the mailbox approves its emails. Anyone else sees From as the address and whose mailbox it is, a note that its owner approves emails from this mailbox, and Assign to the owner, which makes them the task’s assignee. You can still edit the email and ask for changes. When the mailbox stops being usable, the conversation pauses and never switches sender by itself. The task moves to Needs you, From is struck through, and the email says the address is no longer available to this task and why:
  • it was made personal
  • its owner left the brand
  • it was disconnected
  • it needs reconnecting
  • it no longer sends as this address
  • its owner can no longer send for the brand
Continue from another mailbox opens From to choose another sender, and Continue from your own mail moves the conversation to your own mail. Both wait while Heralded could not confirm whether an email went: settle it with It’s in Sent or It didn’t go first. Continuing from the same mailbox and address keeps the thread. Any other address starts a fresh introduction to the same contact. Reconnecting a mailbox that needed it resumes its conversations, and approvals withdrawn while it was unusable need approving again. The API and MCP serve correspondence.sender with its state, account_id, address, pinned, who_sends and paused_reason. state names where the emails go from once one went or you continued from a sender, and is unset until then. pinned says whether someone chose the sender. Before anyone does, account_id and address name the brand’s one shared mailbox, when it has one. who_sends is heralded for a mailbox and member for your own mail or a task you took over. On your own mail, address is null until a copy names it. paused_reason is read from the mailbox and its access each time, so paused_at is always null. A copy from the address of any of your workspace’s mailboxes, including one that needs reconnecting, is attributed to that mailbox, never to a person’s sign-in.

Emails with a source

The task’s pane is its brief. It opens with one sentence on what happened and what is asked of you, then at most one boxed item: their offer with its price, or the email due next. Steps and Why follow. Its main button opens the emails: Review, Respond, Review the follow-up or Reply. Nothing in the pane sends an email. The emails open as the task’s full page. Earlier emails show one line each and open when you select them; the newest is open. An email of theirs shows their new words, and … shows the rest of it, such as the mail it quotes. Show in English sits beside the sender of an email in another language. An offer sits under the email that made it, with Edit their offer. Each option shows its price, deliverable, duration, labelling, conditions and who writes it, with its own Agree and Offer less. Earlier offers are collapsed with your answer beneath them. Until an email carries your answer to them, it reads Not sent yet, such as Not sent yet: you’re offering EUR 600 for a guest article. The email due next is a reply card: who it goes To, which is another person they named where they named one, and From, the language it Writes in, the words with each gap as a field labelled with what it needs, the reminders it covers with Edit, and its own buttons. An answer lists the asks it settles under Answers, with Leave one open to keep one for a later email. The line beside the main button says what pressing it does, or why the email can’t go yet, such as Fill in 1 gap to send. The count includes gaps in the follow-ups it covers. Gaps save when you leave the field or press Enter, or Ctrl+Enter or ⌘Enter for several lines. The main button saves every filled gap before approving and opening or sending the email. The properties column shows the Contact. When an email goes from your own mail, the main button names what goes, such as Open in your mail or Open reply in your mail: it approves the email with its reminders and opens it in your mail app, addressed, under its subject and with your brand’s Heralded address in BCC. Send with that copy to record the email on its task. Send from the email on your Heralded account or a verified alias of the brand’s connected Gmail account, with permission to start work on that brand. Once it is approved, the card offers Mark as sent for a copy that is missing. Once the first email has gone, Write to them sits above the emails. ⋯ beside it holds They replied, or They replied elsewhere while your mailbox sends, and I replied, to paste an email they sent or one you sent from your own mail, Add their terms for a price they gave by phone or in a file, Take over the emails, after which Heralded writes nothing unless you ask with Write to them, and Copy Heralded address. Viewers read the emails and have none of these. From chooses who sends each conversation, and its follow-ups use the same choice. After you open an email in your own mail, record its copy before switching back to a mailbox. Forward a reply to the same address. Heralded adds it to its task when it can match it. A copy of your own email to a contact several tasks write to goes on the task whose approved email it is, word for word above your signature. If several tasks may fit, each one’s status reads Choose a task for an email. The task asks which task the email is for, naming it as Your email to the contact for a copy of your own email, or A reply from the contact for a reply you forwarded. It shows the email and one row per task that fits: Keep on this task, and Move to each other task. Choosing one removes the question from the others. Not about outreach discards the email. If no task matches, Needs you asks the same question. Open it, search the brand’s open outreach tasks by site, choose one and press Add to this task. Not about outreach in the menu discards the email. An email to a source comes with two reminders, which you review beside it. Approving the email approves its reminders with it, and editing any of them asks for your approval again. When Heralded rewrites an email, its unapproved reminders arrive with it. In the same thread, a reminder you edited or approved keeps its words. An introduction to a new contact has its own reminders. Each email and reminder has its own free redrafts. Every email ends with a sign-off in its write language, then your brand’s email signature on the next line. Only the first email to each contact carries the opt-out sentence. Set your signature in Brand settings → General → Emails, or fill its gap in the first email. Filling that gap also fills its follow-ups. Signature changes update the endings Heralded added to unapproved drafts. An ending you edited yourself stays as you wrote it. Approved emails keep the signature you approved. If an email that needs the change is being rewritten, save your signature when its rewrite is ready. When an email goes from a mailbox, its review offers Approve and send and shows the mailbox it goes from. The email goes in the mailbox’s next working hours, and the task and a message say when, with Undo until it leaves. Undo puts it back for your approval. Heralded sends the reminders you approved with the email, unless new mail arrives or you have already reached the goal. It checks the thread and the page before each reminder. If the thread cannot be read, the reminder waits. Before its first email goes, choose another From on the email to switch. After Mark as sent, or once Heralded sends it, the task waits on the person you wrote to under With your team, as Waiting on their name and the days since. Without a mailbox, on each reminder’s date, three working days after the email and a week after that, it comes back to Needs you with the reminder ready to send, and Skip it moves on to the next one. A week after the last reminder, it asks once whether they replied, and closes as No reply recorded if nobody answers within 14 days. A reminder you have not approved is rewritten when the email it follows changes, or when what is still open changes, and follows up only on what is still open. One you approved keeps its words. An address that asked not to be contacted, or that bounced, can’t be given for a task: Heralded says which, and since when. Give another address after an email reached them, and the next email is a first email to that address, drafted for your review. When an email bounces, the task comes back to Needs you. Heralded offers the next contact it finds on the site, or you can give another address. A found contact changes nothing until you choose it. In the pane or on the emails page, choose one, then Redraft for that address opens the email for your approval. If the first email bounced, its greeting and both follow-ups update together. If a reply or follow-up bounced, Heralded writes a fresh introduction that carries the earlier conversation, its open question and any answer you already sent. If that answer and your brand facts cannot answer the question, you fill a gap before approving it. Its greeting names the new contact, or the site’s team when no name is known. An address Heralded may not write to is refused there, with why and since when. The next email to a new address after an email arrived starts its own thread. When an email was not delivered for a moment, Heralded sends it once more the next working day and says which email it resends. With a mailbox, replies in the thread appear on the task after the next sync, within ten minutes. An email you send in that thread is recorded as yours. New mail from an address you have written to, outside the thread, is offered for you to assign, and joins only one task across brands. Heralded keeps no text from other mail. A week after the last reminder, a connected task closes as No reply. Without a mailbox, paste their reply with They replied. Heralded checks whether it is an automatic reply before cancelling any remaining reminder. It reads a person’s reply, in any language, and says in one sentence what they said. What happens next depends on what they wrote:
  • A question or a request. The task comes back to Needs you with one answer drafted that covers everything they asked. It uses only your brand profile and brand facts. Anything those don’t hold, such as a price, a login or billing details, is a gap you fill before the answer can go. The answer comes with two reminders, as a first email does. Something they ask again counts once, and something they no longer want is dropped. A request the answer leaves for later stays open, and the next answer covers it. So does every request when you send your own email in place of the drafted answer, or change its text in your mail. Something they want only after another step, such as a review after they receive your test account, waits until that step is done.
  • A price. It shows as their offer. Choose Agree or Offer less on the option you want. Give a lower amount in that option’s currency with Write my offer. Ask for a free mention and Decline answer the whole offer. Heralded rewrites your reply to name your choice. An option they write needs no content credit. If you supply the article, choose who writes it, with Heralded’s content credit stated before you agree. If they have not said who supplies it, you choose. One answer stands per offer, whoever on your team gives it. A change to its price or material terms opens a new offer; a restatement does not, except their reply to your counter or your ask for a free mention, which opens the offer again for your answer. You can correct an offer, or add one they gave by phone or in a file. Once you agree to a price, the task is tagged Sponsored.
  • They agree to do something. No reminders go. The task waits until the date they gave, or 14 days, and comes back to Needs you with a friendly check drafted if nothing has happened by then. Skip it lets that check go unsent and waits 14 more days.
  • Your side of a deal. Agreeing to an option lists the material it asks you to provide under Your side, such as a test account. Something they already asked for counts once. Choose Mark as done as you complete each item. While any is open, the task is yours, with no reminders. Once the last one is done, the task waits for what they committed to, with no reminders, or for their answer to your email, with its reminders still to go. An email you send that leaves something open, such as a logo you send tomorrow, keeps it under Your side.
  • An away notice. The task keeps waiting and keeps your approved emails. A later human reply clears the away date. Otherwise, the next reminder is due no earlier than two working days after they are back, and an approved email already scheduled moves to that day. While Heralded checks whether a new email is an automatic reply, or if it could not tell, nothing in that conversation goes.
  • A no. A refusal that also asks something gets an answer. A plain no closes the task as Declined.
  • A request to stop. The task closes as Opted out. Heralded never writes to that address for your brand again and stops suggesting the site.
Each offer option shows what you need to provide. Shared conditions and payment timing appear once on the offer. An option with different payment timing shows it on its own row. Your side appears in the pane and on the emails page when you have something to provide now, each with Mark as done. What you owe only after they act, such as payment once they publish, joins it when it can be done. Prices and payment timing are information only. Heralded states them in your agreement email and keeps payment requests in the thread. You handle payment yourself and decide when to send the article. The API and MCP action read include each option’s key, deliverable, duration, labelling, conditions, writer and requirements. A new option gets a key from its deliverable kind, amount and currency, with a suffix for duplicates. A restated or amended option keeps its key, including when a listing with a review is described as a review with a listing. When one option changes, the other options stay available. Their labelling and conditions keep their scope. writer is brand, them, none, or null when uncertain. requirements includes a word band, link count, topic and deadline where given. A single word count becomes a ±10% band; an explicit range keeps its limits. The word band’s optional stated field keeps about or range. requirements.words_asked, also in terms.requirements, serves the whole phrase, such as 900–1,100 words or about 1,000 words. The deadline is when they need your material, separate from their publication date. Conditions shared by every option stay on the offer. With one option, labelling and conditions live on the offer; the option’s copies are empty. Distinct conditions from both levels are kept. Each option’s terms combines its labelling, conditions and requirements with the whole-offer terms. The card and an ordered article use these combined terms. The raw fields keep their scope for editing. Materials needed only for an undecided paid option stay in that option’s brand_owes, as instructions you will see under Your side, and are not repeated in conditions. Billing details, logos and descriptions stay open requests. Once you accept an option, its material asks become requests. A change to who writes an option, what it requires or when they expect to be paid awaits your new decision before it becomes work. Each option states its needs_article and article_credits. payment_due says when they expect to be paid: upfront, or after_publication once it is live; an option carries its own only where it differs, and its terms holds the one that applies. Decisions keep the zero-based option and add option_key; older offers without keys use the index. The conversation’s obligations excludes payments; payment requests do not change whose move it is or hold publication waits. Heralded only reads what a reply says. Nothing in an email can make Heralded send, pay or fetch anything, and every email goes only after you approve it. If a reply can’t be read, the task comes back to Needs you with the reply as it arrived. Once the first email has gone, choose Write to them at any time to have Heralded draft an email that says what you ask. This also retries any replies that could not be read, even when no more redrafts are available. Emails wait until those replies are read.

The article an agreement needs

When they agree to publish an article you supply, free or paid, agreeing also says who writes it. Heralded writing it takes one content credit before your answer can go. With no credit left, your answer isn’t recorded, the offer stays open and you’re offered a way to get credits if your role allows it. Writing it yourself costs nothing. The article is the task’s asset and never a row of its own in Work. The task’s steps grow Write the article, Review and approve, Send to the site and Published. Heralded writes it as a piece, in the site’s language, from what was agreed, what they asked for and the date they need it by. The length the agreed option asks for is the piece’s own length: about 1,000 words is written to between 900 and 1,100. Open it from the task’s asset and choose Approve. Approving the article sends nothing. Heralded then writes a short email that goes with it, and the task shows that email with the article below it. Read both and choose Approve and send, or Ask for changes on the email. With your brand’s mailbox connected, the email and the article go from it as one email in the same thread, in the mailbox’s working hours, with Undo until it leaves. A change to either after you approve asks for your approval again, and a resend after a temporary delivery failure sends the same email and article. An article you wrote yourself goes from your own mail. Without a mailbox, Copy and open in your mail copies your email with the article below it, formatted, and opens a reply in the same thread to paste it into. If your browser refuses the copy, the reply opens with your email, and Copy the article gives you the article to paste below it. A copy of that email to your brand’s Heralded address marks the article sent when it carries the approved article. For a revised article, an article you wrote, or any other copy, choose Mark as sent. The article header reads Ready to send to the site after approval and Sent to the site after it goes. Its publication step names the site that publishes it. The task then waits for them to publish it, with no reminders. The wait runs to the date they gave for publishing it in the agreed offer, including a promise kept through a counter or an edited offer, or later in the conversation. A promise they made with an offer they then replace with new terms counts only if their new email makes it again. Otherwise it runs for 14 days. If the date they need it by passes before the article goes, the task comes back to Needs you with a request for more time drafted. When they ask for changes to the article you sent, each request shows on the piece as one note from them, and the piece comes back to your review. The version you sent stays as it went, and the revision goes only after you approve it. A publication link on another site brings the task back to Needs you with a reply asking for the link on the agreed site. The task completes at the address the article is published on. Heralded learns it from a link in their reply or the live link you add with Add the live link, whoever wrote the article, and reads that page: if it names you, the task completes there. If it is live without naming you, the task comes back to Needs you saying so. A daily update or weekly report that finds that page naming you completes it the same way. One that finds another page of the site naming you completes the task too, and the article keeps waiting for its own address. A task to be named on a site completes when a page on that site names you, and its results start from then. A correction completes when the page no longer says what you asked them to correct. Co-marketing completes when you confirm it is live with Mark done, which Heralded asks for once they agree. A reply that arrives after a task completed is kept and read, and doesn’t change its results. A reply that arrives after a task closed unanswered opens it again. What the emails say is kept for 13 months after the task closes. Heralded doesn’t suggest a source whose emails closed in the last 90 days, or one that asked not to be contacted. Pausing your brand pauses its reminders and waits. When you resume, each one restarts with the days it had left. A date the source gave you doesn’t move, and a task whose date passed while your brand was paused comes back to Needs you.

Done and verified

When a daily update or weekly report no longer finds an issue you worked on, the action waits in Needs you for Confirm fix or Not fixed. Delivered actions appear in Results. A qualifying page citation makes an action Cited. A verified gain makes it Paying off. Otherwise it stays Delivered, with its measured outcome or reason. The pane keeps citation evidence and measurement separate. Verifying actions explains the tests and windows. If you marked work done by mistake, Undo in its message returns it to Needs you until you mark it done again. Its earlier delivery stays in the thread. A failed site write returns to Needs you, even if the site took the write but still serves the old value. Setup items finish as Done when their setting or connection is in place. They have no measured outcome. For work notifications, see Email and Slack.

Write language

Open outbound actions carry write_language, write_language_source and write_language_locked on action lists and detail reads in the app, /v1 and MCP. Lists carry the stored choice, which is null on an older action that has none yet. A detail read resolves a missing choice for display with source auto, without changing the stored action. Choosing a language or starting the work stores it. A member’s stored choice is kept. Outreach and correction drafts use the recipient page’s language. For a source found in Google results, that is the ranked page. Community replies use the thread’s language. An unknown third-party language defaults to English. Each outreach angle is in English. Page work uses the page’s established language and locks that choice. An unknown brand page uses the market’s local language until a language is established. On the emails page, an email or drafted reply in another language offers Show in English once its translation is ready. Show original switches back. You edit and send the original. The task’s opening sentence stays in English. Action detail reads in /v1 and MCP include each email’s language and stored english_text, and each translated draft’s english_body. Each email also serves new_text, its new words without quoted mail, and body_format, either plain or markdown. When the reply cannot be separated safely, new_text is null and the full text stays available. party_name supplies the stored contact name first, then the email’s display name, then the address. An email from another address shows that sender’s name. The contact name also labels the wait, the email due next and its steps. Your own-mail copies show You. Mailbox copies name the sending address. Action rows and drafts show Writes in with their language. The pane shows it on the email or draft while it can change, and the full page shows it under Language when Heralded writes text for the action. An ordered piece keeps the language recorded on its order. Choose Change to change an unlocked action’s write language before a content order or site change starts. A locked choice, such as a page rewrite in the page’s own language, offers no Change; its info button says why. A language change starts a new short draft, uses the same free redraft allowance as requesting changes, and keeps earlier versions unchanged. Request changes also lets you choose the next draft’s language unless the action is locked. Before you start a filed content action, its full page shows Language with the resolved language and Change. Studio’s piece header shows the language recorded on the order. An older draft without a recorded language shows the action’s resolved language in its piece header and draft reads, without changing the draft or its timestamps.

Content Studio

Long pieces open in their full work page’s asset editor. You can edit the draft, apply comments, check statements, compare versions and export the piece there. Articles, guides, comparison pages and product pages also have featured images and social previews. Approve the piece, publish it on your site and add its live link. Heralded does not publish it for you. Studio links open the full work page.

What an order carries

Heralded orders each piece with what it holds about the action: the kind of piece, its subject, the competitors it answers and the buyer questions from the questions it is linked to. Alongside these go the AI answers to those questions and the pages they cite, with the text Heralded read from each page. The writer also gets up to three of your topic’s candidate pages whose text Heralded holds, each with its title, search description and page text, up to 2,000 characters. What Heralded found, such as a topic’s monthly searches, and the figures it counted, such as how many answers named a competitor in your place, go to the writer as evidence it may cite, never as instructions. A rewrite also carries the page’s current text. When a piece targets keywords, its order carries up to ten, ordered by demand and the gap to close. A keyword that is no longer a problem comes last. Pages ranking for its targets and the domains AI cites lead the supplied sources. Its topic verdict, buyer questions and evidence come from the action’s topic. The piece keeps a write language when its action is filed. For question targets, it uses the observed language of the answers. Mixed or unknown languages use the market’s local language, or English for Global. Page rewrites use the page’s established language. Each order and short draft keeps the language it was written in. Your brand facts reach the writer too. Adding, editing or removing a fact in Brand settings updates what the writer holds, and the writer may state your facts in any of your pieces. After approval, the action waits in Needs you as Approved, ready to publish, and Add the live link in the page header opens a field in the work bar. Enter the address and select Save beside it. The live link appears in the bar once publication is recorded. The action is done and Heralded watches the page for citations. The page header always shows one main button for the stage the piece is at. While the writer works, the work bar shows what it is doing. Export in the draft’s meta line offers these exports of the saved version.
  • Copy as Markdown and Download .md include the title and description as YAML front matter, followed by the body.
  • Copy HTML includes the body only.
  • Download .html includes the body, with your meta title and meta description in the document’s title and description tags. Articles use their title and, when there is no meta description, their summary. Without a title field, the export uses the piece’s title. Download filenames use the same title.
You publish the words on your own site. When Heralded first finds an AI engine citing the page, the action timeline records its first citation once and names the engine. Each piece costs one content credit, with included AI edits. Short drafts, such as a title and description, an outreach email or a review reply, cost nothing. After you save an edit of a draft, the writer checks the new version and applies the fixes it is sure of itself. You review the settled result. A check that fails permanently fails that operation and does not create a settled version. Review describes stopping and resuming a piece, the free retry after a failure and starting over. A brand pause or a writing-budget pause keeps the piece waiting without failing it or returning credits. If approval is refused, the draft returns to your review with the reason in its thread. Your draft stays available and its credit stays spent.