Campaign Rec Filename: every variable you can use

The Campaign Rec Filename field decides what each saved recording is called. It applies when Campaign Recording is set to ONDEMAND or ALLCALLS, and it takes a string built from a fixed set of variables. The variables get swapped for real values at save time, so a template turns into a unique name for every call. Get the pattern right once and you never have to rename a file by hand.

The standard variables

You can mix and match these in any order, joined by underscores or other plain characters. CAMPAIGN is the campaign ID. INGROUP is the inbound group for a call that came in through an Ingroup. CUSTPHONE is the customer phone number. FULLDATE and TINYDATE are two date formats, and EPOCH is the Unix timestamp. AGENT is the agent user ID. VENDORLEADCODE pulls the Vendor lead code from the lead, while LEADID, CALLID, and RECID give you the lead, call, and recording identifiers respectively.

The default is FULLDATE_AGENT, which produces something like 20051020-103108_6666. A common alternative is CAMPAIGN_TINYDATE_CUSTPHONE, which resolves to a name like TESTCAMP_51020103108_3125551212. Both are readable at a glance, which is the whole point: a good filename tells you who, when, and which number without opening the file. Notice that the variables are written in plain uppercase with no special syntax around them, and the underscores and any other plain characters between them are kept as literal text in the final name.

How a template becomes a filename

flowchart TD
  A[Call ends] --> B[Read Campaign Rec Filename template]
  B --> C[Swap each variable for a value]
  C --> D[FULLDATE becomes timestamp]
  C --> E[AGENT becomes user id]
  C --> F[CUSTPHONE becomes number]
  D --> G[Join into one name]
  E --> G
  F --> G
  G --> H[Check under 90 characters]
  H --> I[Save the recording file]

There are also four POST variables for dialers that run POST recording processing: POSTVLC, POSTSP, POSTARRD3, and POSTSTATUS. These alter the filename after the call finishes and replace the token with a value from a default field, so they land later than the standard set. They are covered separately in our writeup on POST recording filename variables.

The rule you cannot ignore

The resulting filename must be under 90 characters. That sounds generous until you chain several variables together. A long campaign ID plus FULLDATE plus a full CUSTPHONE plus VENDORLEADCODE can creep close to the limit, and once a real value is longer than your test value, you can blow past it without noticing. Keep templates lean: pick the two or three variables that actually help you find a file later and stop there. TINYDATE over FULLDATE saves you several characters per recording if you are tight on space, and EPOCH is shorter still if you only need a sortable timestamp rather than a human-readable one. The safest move is to write out your template, substitute the longest realistic value for each variable, and count the characters before you commit it.

Your naming scheme should match how you search. If your team finds files by Agent and date, lead with AGENT and a date variable. If you reconcile recordings against a CRM by lead, put LEADID up front. Either way, the same name shows up in the recording report, so a tidy template pays off every time someone goes looking. For the practical naming recipes, see how to name recordings by campaign, date, and phone.

Filename templates are one small piece of a wider recording setup, which we cover end to end in our call recording guide. If you would rather not babysit any of this, our managed dialer ships sensible recording defaults out of the box. See our pricing to see what is included.