Contact and company records

Twenty stores people and companies with their linked fields and notes. On a trigger such as an inbound form or an updated email, a Beam agent reads the matching record, applies the edit your team approved, and writes it back where permissions allow, for example filling a missing job title. Clean, unambiguous updates save on their own. A record that matches two contacts, carries a field your rule marks as manual, or would overwrite a value someone recently changed is set aside for a person to resolve before the agent saves it.

Opportunity pipeline updates

Twenty tracks opportunities through pipeline stages with amounts and close dates. When an event your team defined occurs, a signed document or a paid invoice, a Beam agent reads the linked opportunity, checks the approved condition, and moves the stage or updates the amount where the connector allows. Standard advances happen automatically with a note attached. A deal that skips required stages, carries a value above the threshold you set, or lacks a needed field is flagged instead, and a person reviews the numbers before the change is committed.

Activity and note entries

Twenty keeps activities and notes tied to each record. A Beam agent reads incoming context, such as a call summary or an email thread, and writes a structured note onto the right contact or company where your rules permit, so the timeline stays current without manual entry. Clear, well-matched entries are added directly. When the agent cannot tell which record an activity belongs to, or the content includes something your policy marks as sensitive, it holds the note and asks a person to place or approve it before anything is written.