Personalizations allow you to easily customize your query letters.
Writing query letters to agents is repetitive work, but it shouldn't be. You'll send dozens of queries and most of your letter stays the same: your hook, your book's description, genre, word count, why it's a good fit for publishing.
The only things that change might be the agent's name and a note on why you chose that specific agent.
That's where personalizations come in. Instead of rewriting your entire query letter each time, you write it once with placeholder text for agent-specific details.
One Personalization has already been created for you, allowing you to easily specify the agent's name when creating their query.
Creating a Personalization:
One Personalization has already been created for you, allowing you to easily specify the agent's name when creating their query.
To create a new Personalization:
- Select your project from the sidebar and open "Query Template"
- Expand "Make Query Letter Template" and locate the "Personalizations" section
- Click the green "+" icon to create a new Personalization
- Enter a name for the personalization (e.g., "Agent Connection")
- Enter the placeholder surrounded by double-curly braces (e.g., `{{agent_connection}}`)
- Enter the "Example Text." The "Example Text" demonstrates how the substitution will appear in the "Example Email" and is only used on this page.
- Click the green checkmark to save
- Add your placeholder to the query letter text in the Editor
- In the "Example Email" section on the left, you'll see your example text highlighted, showing how it will look when filled in (this highlighting is for demonstration only and won't appear in actual queries)
- Click "Submit Query Template" when finished
Later, when you create a query for a specific agent, you'll see a similar input box. Fill in the agent-specific text, and Querier will automatically insert it into the query letter.
The graphic below illustrates how to add a Personalizations:

Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article