Generate plays for a contact

Plays are ready-to-use engagement tactics written for a specific contact: subject lines, email copy, and multi-step sequences grounded in what the workspace already knows about that person. This page covers how to generate, regenerate, and remove plays for a contact. For more on what a play produces, see Play copywriting.

This is also where customers used to come to generate a contact’s Digital twin by hand. There is no manual action for that anymore: a contact’s Digital Twin is produced automatically once it is qualified as a fit for your ideal buyer profile, so running (or re-running) Contact qualification is what triggers it now, not a step on this page.

The Generate plays action appears on the contact list (for several contacts at once) and on the contact detail page (for one contact). If you are signed in with a read-only seat, this action control is hidden.

Before you start

To generate plays, you first need at least one play set up and set to Ongoing. The Generate plays window only offers plays whose status is Ongoing; if there are none, you will see “No agents found” with a prompt to create them first. See Play copywriting.
Generating plays consumes credits. See Credits.
Generating plays works best on contacts that have already been qualified and researched, so the output is grounded in real context rather than guesses. See Run a Qualification agent on contacts and Run a Research agent.

Steps

Generate plays (single or in bulk)

To run on one contact, open the contact and choose the Generate plays action in the page header. To run on several at once, go to the contacts list, select the rows you want, and choose Generate plays from the actions bar. Plays can also be started from the relationship map and from the contact side panel.
The Generate plays for contacts window opens. The footer shows how many contacts are selected.
You see a checklist of the available plays. Use the search box to filter by play name or tag, and use Select all or Deselect all to set the list quickly. The window remembers your last selection, so the same plays are pre-checked next time.
Check the plays you want to generate for the selected contacts.
Select Start. The window closes and a confirmation appears that the job was created.

Regenerate or delete plays from the Overview tab

The plays already generated for a contact live on the contact detail page, under the Overview tab, in the Plays card, which shows a count of plays for that contact.

To refresh a single play, open the play row and use the Regenerate action. To refresh several, select the play rows and choose Regenerate from the panel toolbar; a confirmation tells you how many plays were queued.
To remove plays, select one or more play rows and choose Delete, or use the delete action on a single row. The Delete Plays from contact? window asks you to confirm, showing how many plays will be removed. Deleting removes those plays from this contact only; it does not delete the play itself.

Each play row shows a Name, a Status (Generated when the copy is ready, or another state such as Not applicable or Failed), and a Last updated time. Expanding a row reveals the generated copy: a Subject line and the Generated play text, or, for a sequence, each numbered Step. When a play did not produce copy, the expanded row shows a Reasoning note explaining why.

A sequence comes back with one Step for every step the play defines, each written separately and numbered in the order you set them, so Step 3 is the third step of your play no matter how many steps it has. If a step produces no copy, it stays in place as an empty step rather than dropping out, and the steps after it keep their own numbers. That gap is deliberate: it shows you the run was incomplete for that step, instead of handing you a shorter sequence that looks finished. See A step in a sequence came back empty for what to do next.

What happens next

Generating plays runs as a background job, so you do not wait on the screen. Track progress under Agent tasks on the contact’s Activity tab (or in the workspace task feed). While agents are working on a contact, the record shows a working indicator and a note that “Agents are working on this contact…”

Plays appear on the contact detail page under the Overview tab, in the Plays card, each with its status and generated copy as described above. The count updates as plays are added.

The contact’s Digital twin also lives on this page, under the Practice tab, but it is not something you trigger here: until the contact is eligible the card reads “Digital twin is not available yet” and asks you to requalify the contact, then becomes usable on its own the moment qualification clears the bar. See Digital twin for what makes a contact eligible.

If a job ends in an error, see An agent job failed. If a task seems stuck in the feed, see A task is stuck.

Eva precision: this page used to also cover a “Generate digital twin” action (single contact and bulk); that action has been removed from the product. A contact’s Digital twin is now produced only as a side effect of Contact Qualification finding it an ideal-buyer-profile fit - there is no other trigger, manual or otherwise. If a customer asks how to generate or regenerate a Digital Twin, point them at requalifying the contact, not at this page’s Generate plays action. Generated plays surface in the contact’s Overview tab, and the Digital twin sits under the Practice tab (it is no longer a tab of its own).

What Created by shows

The Play Agents list has a Created by column: the person who built that play. You may see an Evergrowth address there rather than one of your own team’s, because an Evergrowth team member often builds your first plays with you during setup.

Created by records authorship and nothing more. It is not an ownership field: it does not affect who can see or edit the play, and it is unrelated to the Owners on accounts and contacts, which govern territory. It does not set who the play is written for either - that is the play’s persona targeting. The address is never inserted into generated copy, nothing is sent to it, and it cannot be reassigned once set. If you want a play authored by your own team, create a new one and reuse the instructions.