Personal lines for each contact

Published by Argorant

Give every contact their own line through a {{custom_...}} variable, correct or clear saved lines, and the limits that apply.

A personal line is one short sentence part written for one contact, for example the kind of customers their company sells to. It goes into your emails through a variable such as {{custom_buyers}}. Your AI assistant writes the lines through the Argorant connector or the API, or you upload them as a file.

Set up the variables

Each variable has a name, an instruction and a fallback. The instruction says what the line says, how long it is and its style, with two or three examples. The fallback is a line that reads well for anyone. Every contact without their own line gets the fallback at once, so the campaign can launch at any time.

We get you 10 to 15 {{custom_buyers}} a month.

With the instruction the customers this company sells to, 4 to 10 words and the fallback customers like yours, one contact reads We get you 10 to 15 restaurants that need payroll help a month. and a contact without a line reads We get you 10 to 15 customers like yours a month.

Write the lines

  • Your assistant lists the contacts still on the fallback, with what Argorant knows about each company, and writes one line per contact from those facts.
  • Show the first five lines to whoever owns the campaign before the rest are written.
  • A contact with no usable facts keeps the fallback. Nothing is invented.
  • A finished file goes up in one go. Use CSV with the columns email (or lead_id) and one column per variable, or JSON. Rows that cannot be used are listed with their row number and the reason, and never stop the rest.

Correct or clear a saved line

A saved line is never replaced by accident. If you send a contact again, the line they already have stays, and the answer lists it as kept, with the saved text and the one you sent.

  • To correct lines, send them again with overwrite set to true. In the command line, add --overwrite to the import.
  • To clear a line, send the variable as null with overwrite set to true. In a CSV file, add a clear column with the variable names, or all. An empty cell never clears anything.
  • A cleared contact gets the fallback again and is back in the list of contacts still to write.
  • Every replaced or cleared line is listed in the answer with the old and the new text, and Argorant keeps a record of each change.

Lines in the middle of a sentence

A line used in the middle of a sentence is saved with a lowercase first letter, so Hiring managers at food plants becomes hiring managers at food plants. Acronyms, names, brands and places such as CFOs, SaaS, Shopify or Chicago stay as written. This follows where your emails use the variable: a line that starts a sentence keeps its first letter. To change that, set the variable's case to sentence_middle (always lowercase) or as_is (exactly as written). Saving the setup brings the lines already saved to the same case.

A contact whose company has no description yet is marked description_status: pending while Argorant reads the company website. Your assistant writes that line on the next round instead of guessing from keywords.

Limits

WhatLimit
Variables per campaign1 to 5
Instruction per variable4,000 characters
Each line and its fallback20 to 300 characters, set per variable (150 by default)
Email text kept with the setup10,000 characters
Where a line came from (basis)200 characters
Contacts per call5,000
Contacts per page of the list still to write5,000
File upload200,000 rows and 50 MB. Up to 5,000 rows are written at once, a bigger file in the background
Calls per hour for each workspace30 setups, 300 writes, 300 status reads and 30 files

Each line is plain text on one line, with no curly braces and no HTML. Links are only allowed when the campaign allows them. See Fallbacks for how variables without a value behave.

Still stuck? support@argorant.com