Talent & VIP Guest Management

Overview

Talent Management is an organization-level CRM (not per-event) for talents, VIP guests, programs, contracts, hospitality, travel, and hotels—complementing event-scoped Speaker module.

Purpose

Maintain long-term relationships with performers, VIPs, and talent rosters across multiple programs and events.

Who should use it

  • Entertainment producers
  • Corporate events teams with VIP lists
  • Talent agents using org-level CRM
  • Presenter Pro+ subscribers

Benefits

  • UUID-based talent records with multi-step profiles
  • VIP guest registrations linked to events
  • Contract lifecycle (draft → sent → signed)
  • Program calendar with talent/guest assignments
  • REST API at /api/v1/

Action Path
Talent hub /talent/
Talent list /talent/talents/
VIP guests /talent/vip-guests/
Programs /talent/programs/
Program calendar /talent/programs/calendar/
Contracts /talent/contracts/
Categories /talent/categories/

Prerequisites

  • Subscription: Presenter Pro+ (talent tool key)
  • CustomUser.account linked to talent_management.Account
  • Separate from speakers_enabled event toggle

Step-by-step — Add talent

  1. Open /talent/talents/create/.
  2. Complete multi-step wizard (contacts, categories, requirements).
  3. Add communication log entries (email, WhatsApp, SMS type, call notes).
  4. Link to programs or contracts as needed.

Step-by-step — VIP guest

  1. Create VIP guest record.
  2. Create VIP event registration linking guest to Nigall event.
  3. Track hospitality and travel records.

[SCREENSHOT: Talent detail page]


Field descriptions

Entity Description
Account Org container; UUID scoped API
Talent Performer/speaker CRM record
TalentContact Agents, managers, assistants
EventVIPGuest VIP identity
VIPGuestEventRegistration VIP ↔ Event link
Program Org program with talent/guest roster
Contract Fee, status, legal documents
Hotel / Travel / Hospitality Logistics records

Communication types

email, whatsapp, sms, call_notes


Business rules

Rule Detail
Account scoping API routes under /api/v1/accounts/<uuid>/
Judges Not implemented — no judge model in talent or speakers
SMS Type exists; delivery depends on provider config
Contract states draft, sent, signed, cancelled workflows via views

Validation rules

  • UUID primary keys on talent entities
  • Account required for API scoping

User permissions

Role CRM access API
Linked account user ✅ scoped
Other users
Staff Admin override

Workflow

flowchart TD Talent[Create talent] --> Program[Add to program] Program --> Contract[Contract] Contract --> VIP[VIP guests] VIP --> EventReg[Event registration]

Examples

Award show: Talent CRM for performers, VIP guests for seating, contracts for fees.

Corporate summit: VIP guests linked to registration events without public CFP.

Best practices

  • Keep CustomUser.account aligned for team access
  • Use contracts for fee documentation even when speakers module also used
  • Calendar feed for executive visibility

Tips

  • Calendar iCal feed: /talent/programs/calendar/feed/
  • API for integrations: see API Reference

Common mistakes

Mistake Result Fix
Confuse with Speakers module Duplicate data Speakers = event CFP; Talent = org CRM
No account link Can't access API Link user account

FAQs

Is this the same as Speaker Management?
No — Speakers is per-event applications; Talent is org-level CRM.

Judge scoring?
Not implemented — roadmap only.

Troubleshooting

Symptom Cause Fix
404 on API Wrong account UUID Use /api/v1/accounts/ list
Empty dashboard No account FK on user Admin link account

Screenshot placeholders

  • [SCREENSHOT: Talent list]
  • [SCREENSHOT: Contract detail]
  • [SCREENSHOT: Program calendar]

Administrator notes

  • Link CustomUser.account in Django admin
  • Enterprise customers may need multiple accounts (manual)

Developer/API notes

Resource Endpoint pattern
Accounts GET /api/v1/accounts/
Talents /api/v1/accounts/<id>/talents/
VIP guests .../vip-guests/
Contracts .../contracts/
Categories .../categories/

ViewSets in talent_management.api.views.


See also: Known Limitations