Dashboard
0%
1
Curious builder0 XP earned · 300 to level 2
0 daysFinish a lesson to begin
Badge collection0 of 6 unlocked
51 small wins to finish your pathNext question →

Q37HardSystem design

Design an agent that turns sales call recordings into CRM updates for a 500-person sales organisation.

30-second answerSay your answer out loud first, then reveal.
Call recordings are transcribed with diarisation and combined with calendar and CRM context for LLM extraction into a schema, mapped to CRM fields and validated, then shown as suggested updates that the rep approves into a CRM write-back or that auto-apply for low-risk fields, with the write-backs feeding pipeline and coaching analytics.

Key decisions

  1. Matching the call to the right opportunity: use calendar invites, attendee emails and account domains. Ambiguity means asking the rep.
  2. Schema per customer: each sales org has its own fields and methodology (MEDDICC, BANT). Make the mapping configurable.
  3. Trust and control: reps hate wrong CRM data. Default to suggestions with diff views; auto-apply only factual, low-risk data (activity logged, call summary note).
  4. Field validation: picklist values, stage transition rules (can't jump from Discovery to Closed Won), date sanity.
  5. Privacy and consent: call recording laws vary by region; customer data in transcripts; retention policies; access limited by role.
  6. Evaluation: a labelled set of 100 calls with correct field values; measure field-level precision and recall; track the rep acceptance rate in production.

Value metrics: CRM data completeness, time reps spend on admin, forecast accuracy, manager visibility.

You understood something today that you didn't yesterday.