Amplify Enrich Best Practices

Amplify Enrich helps you generate, standardize, and maintain record data automatically across your database. The quality and consistency of your results depends on how clearly your prompts and fields are defined, and how well your Enrich workflows align with your team's day-to-day processes. These best practices will help you get meaningful results from the start, build recruiter confidence, and refine your setup over time.

Enrich Automation Step

Start with a Clear Goal for Each Prompt

The most effective Enrich configurations are built around a specific workflow gap — a field that's consistently left blank, a task that takes too long, or information that's hard to find across a record. Before building a prompt, identify exactly what problem you want it to solve and what a good output looks like.

A clear goal makes it much easier to write a prompt that delivers consistent results, and gives you a benchmark to measure against when reviewing outputs.

Aim for First-Time Usability

A well-configured Enrich prompt should produce output a recruiter can use without editing. If users are routinely adjusting generated content before it's useful, that's a signal to refine the prompt rather than accept the extra step as normal.

Each revision a user makes adds friction and reduces the time saving the prompt was meant to create. Tightening your prompts to reduce back-and-forth is one of the most impactful things you can do to improve adoption and efficiency.

Build in a Feedback Loop

Prompt quality improves with use. Once your Enrich automations are live, monitor how they're performing and gather feedback from the people using them.

A simple feedback loop might include:

  • Checking the Activity Feed in Automation to see which records are passing through your Enrich steps and whether they're completing successfully.

  • Asking recruiters directly whether the generated content is useful, and where it falls short.

  • Updating prompts regularly based on what you learn.

Releasing a prompt before it's perfect is better than waiting. Even output that gets recruiters 80–90% of the way there represents a real time saving, and the remaining improvement will come from feedback once it's in use.

Use Enrich to Drive Consistency

One of the strongest use cases for Enrich is standardization. When every new record entering your database is enriched the same way, with the same key information in the same fields, your users always know where to look. That consistency reduces time spent navigating records and helps recruiters act quickly.

Consider using Enrich to:

  • Automatically generate candidate profile summaries when a new record is added

  • Standardize job descriptions across your database

  • Populate fields that are consistently left blank during manual data entry

For ideas on using Automation for data standardization more broadly, see Automation Data Hygiene Use Cases.

Test Before Going Live

Always test a new prompt on a sample of records before activating the automation. Check that:

  • The output format is compatible with the target field

  • The content makes sense across different record types

  • Edge cases such as records with missing or incomplete data behave as expected

Testing early prevents unexpected overwrites and ensures your users encounter the prompt at its best from day one.

Enrich from Notes

Iterate Rather than Switch Off

It's unlikely every suggestion will be right 100% of the time, especially when you first go live. Resist the temptation to disable the feature if early results aren't perfect. Even if 80% of suggestions are accurate, that still means 80% of your configured fields are being kept up to date with information that would otherwise rely on manual entry.

Use field descriptions to refine suggestions over time. The more specific and accurate your descriptions are, the more consistent the output will become. Small adjustments — such as adding formatting guidance, or clarifying what should or shouldn't trigger an update — can make a significant difference.

Choose Fields that Reflect Real Conversations

Configure fields that are genuinely likely to come up in the notes your recruiters write every day. The best starting point is your most common note types (e.g. call summaries, intake notes, check-ins) and the details that regularly get captured in them.

Good candidates for enrichment include fields that change frequently and matter for day-to-day decisions, such as:

  • Availability or start date

  • Location or preferred work area

  • Current or desired job title

  • Employment type or salary expectations

Avoid configuring fields that rarely change from a note, such as a candidate's name. These are unlikely to yield useful suggestions and add noise to the review process.

Use Note Templates as a Starting Point

If your team uses note templates or standardized intake forms, these are a natural guide for field selection. Fields that map to information captured in those templates are exactly the ones most likely to generate accurate, useful suggestions.

For example, if your job intake form always captures start date, bill rate, and work location, those are strong candidates for your job entity field configuration.

Write Specific Field Descriptions

The description you add to each configured field acts like a prompt. It tells Amplify what kind of information belongs there and what to look for in the note text. Vague descriptions produce inconsistent suggestions; specific ones produce reliable ones.

Where relevant, tailor your descriptions to reflect regional or business-specific formats. For example, if a field uses a default description suited to US formatting, such as a zip code, update it to reflect the format used in your region, such as a UK postcode. You can also include directives like "If unsure, do not suggest an update" to reduce low-confidence noise.

Always Review Before Saving

Enrich from Notes suggests updates — it doesn't apply them automatically. Encourage your users to treat the review step as a quick, lightweight check rather than a burden. In most cases it takes only a moment to confirm the suggestions look right before saving the note.

Summary

To get the best results from Amplify Enrich, keep this checklist in mind:

Enrich Automation Step

  • Define a clear goal before building each prompt.

  • Aim for output that's usable without editing.

  • Monitor performance and gather user feedback regularly.

  • Use Enrich to standardize records and drive database consistency.

  • Test on a sample of records before going live.

Enrich from Notes

  • Iterate on field descriptions rather than switching the feature off.

  • Configure fields that reflect the information captured in everyday notes.

  • Use note templates and intake forms to guide your field selection.

  • Write specific, detailed descriptions to improve suggestion accuracy.

  • Encourage users to review suggestions as a quick, lightweight step before saving.