Save and tag calls from a shared dashboard

Edit fields lets the people you share a dashboard with change a few custom field values on a call, straight from the shared link. Use it to let a manager save the calls worth keeping, tag a call with a topic, or mark one as reviewed. Viewers do not need a Speak AI account, and you choose exactly which fields they can change.

What viewers see

Open a call from the shared dashboard and look at the tabs beside the transcript. An Edit fields tab sits next to Fields and appears only when you have turned editing on for at least one field.

1. Pick your name in Editing as. You can search the list. If the owner allowed it, choose Other (type a name) to type your own.
2. Set the fields. A field that takes one value is a dropdown with a Not set option, and a field that takes several values lets you choose any number. If the field allows it, Other (type a value) adds a value that is not on the list.
3. Click Save changes. The tab says Saved when it worked. Discard changes puts everything back. Your name is remembered in that browser, and Save changes stays off until you have chosen one.

Only the fields you changed are sent. Saving changes the call itself, so the new value is the same one your team sees in Speak AI.

Save a call

To save a call from a shared dashboard, open it, pick your name in Editing as, set the Saved field (or whichever field your team uses for it) in the Edit fields tab, and click Save changes. The call then appears in the dashboard’s Saved calls view.

Turn on Edit fields

Edit fields is a setting on the dashboard. You set it with the update_dashboard tool or the dashboards API, under settings.fieldEdits.

{
  "settings": {
    "fieldEdits": { "fieldIds": ["FIELD_ID_ONE", "FIELD_ID_TWO"] },
    "feedback": {
      "isEnabled": false,
      "fieldIds": [],
      "submitters": ["Alex Rivera", "Sam Chen"],
      "removeReasons": [],
      "allowOtherSubmitter": false
    }
  }
}

What each part does:

• fieldIds lists the fields viewers may change. The order you list them is the order they appear in the tab. You can list up to 50, each once. Ids that are not fields of your workspace are dropped when you save. Send "fieldIds": [] to turn editing off and remove the tab.
• Allowed values. Every field you list needs a list of allowed values, such as a dropdown or a multi-select. Saving a field without one returns an error that names it.
• Visible fields. A listed field also has to be one the shared pages show. If you pick specific fields for the Fields tab, include the editable ones. A field that is hidden or inactive is left out of the tab.
• No AI prompt. Choose fields that Speak AI does not fill in for you. A value that comes from an AI prompt can be written again when the call is analyzed again, which would undo what a viewer saved.
• Names. The Editing as list comes from feedback.submitters, the same names the Feedback button uses. With allowOtherSubmitter on, viewers can type a name that is not on the list. With an empty list and allowOtherSubmitter off, viewers type any name in a text box.

Leave fieldEdits out of an update and the saved value stays. Each section of settings is stored on its own. See Labels and comments on a share link for the other viewer settings.

Build a Saved calls view

A saved call is only useful if you can find it again. Add a table widget to the dashboard, ideally in its own section called Saved calls:

1. Set the table to list records, one row per call.
2. Add a column for the field viewers edit, such as a Saved dropdown.
3. Filter the table, or the whole dashboard, to the value you care about, for example Saved: Yes.
4. Leave row clicks on, so a row opens the call.

A viewer saves a call in the Edit fields tab, and it shows up in the Saved calls table a few minutes later.

Things to know

• Numbers lag a little. The change is stored at once, but widgets on a public link are cached. Expect up to four to five minutes for a date range that reaches today, and about fifteen for a range that has already closed.
• Several values are stored as one text value. A multi-select field keeps its choices together, separated by commas, so a custom Other value cannot contain a comma and filtering by one single choice inside the list is limited. Use a single-choice field when you need exact filters.
• Limits. A text value can be up to 500 characters and a multi-select up to 50 values. A field that takes one value rejects a second one.
• The link is the key. Anyone who has the link can edit the fields you listed, and the name they pick is not checked against a sign-in. Password enforcement for edits is coming; until then, share the link only with people you trust to edit.
• You get a notification. When a viewer changes a field, the dashboard owner gets an in-app notification that names the person, the field, the new value and the call.
• Links expire with the plan. If your subscription lapses, the link stops working, and so does editing.

Related: Dashboard sharing · Widgets · Custom fields