STAGING · DB=togra_stagin · changes here do not affect prod
Eolas · Togra Log in →
Eolas · Workflows

Agents & writers CRM — roster, interaction log, follow-ups

Last verified 7 Jun 2026


# Agents & writers CRM

Forbairt → Agents & writers is the development team's relationship layer: a
roster of the agencies and people you deal with, and a log of every interaction
so the slate remembers what was sent to whom and what you owe each contact next.
It sits alongside Buyers (which is the sell-side roster — broadcasters,
streamers, distributors, sales agents, financiers); Agents & writers is the
talent-side roster.

The roster

  • Agencies — talent agencies, literary agencies, management companies, production companies. Name, kind, country, website, notes.
  • People — agents, writers, directors, execs. Filed under an agency, or kept as freelance / unrepresented. Each has a role, email, phone and a last-contacted date that updates automatically as you log interactions.

The interaction log (the memory)

Against any contact you log an interaction — a submission, call, meeting,
email or offer — with a direction (you sent / you received), a date, an optional
project, a summary, and an outcome (pending / positive / passed / no
response / actioned). Set a next-step + next-step date and the follow-up
surfaces in your approvals inbox when it falls due (and by email if you enable
the Agent / writer follow-up due rule on the Notifications page). This is what
stops the same agent being re-pitched from memory, or a follow-up slipping.

Footprint

Each contact card shows two cross-slate views:

  • Attached on the slate — projects where the contact's name matches a talent-register attachment (a writer's / director's own attachments).
  • Represents on the slate — talent attachments where this contact (or their agency) is the recorded rep. You set that link on a project's Packaging page: each attached talent now has a rep picker listing your agencies and agents, which writes to the talent attachment's rep field. So an agent's client list across the slate is exact, not guessed.

Where it connects

  • Pitches (dev_pitches) remain the record of pitching a *project to a buyer*; the CRM is about the agent / writer relationship over time.
  • Packaging sets the rep on a talent attachment (lighting up the talent register's rep field), which drives the "represents" footprint.
  • Agencies and people are in global search (⌘K) — find an agent or writer and jump straight to their card.

Sources

  • · agents.php
  • · lib/agents_crm.php (agencies / agency_people / agency_interactions, mig 275)
  • · lib/notification_rules.php (agent_followup_due)