Open a person or a company in FirstIgnite and a badge tells you where it stands in Minuet. From there you can confirm an uncertain match, link the right record, or create one that isn't there yet.
Before you start: your team needs the CRM panel operation on for the badge to appear at all, and Send organizations & contacts to create new Minuet records rather than only link to existing ones. Both live in FirstIgnite under Minuet Settings (app.firstignite.com/inteum/settings). To turn them on, a team owner or admin opens Minuet Settings in FirstIgnite and scrolls down to Operations. See What each Minuet feature needs, and who can turn it on.
The Operations section of Minuet Settings in FirstIgnite, with a toggle for each operation
To send many records at once instead, see Sending a list of companies and contacts to Minuet CRM.
Links are per team. The same person linked by one FirstIgnite team is unlinked for another.
What the badge is telling you
Badge | Meaning | Clicking it |
Checking Minuet… | First lookup running | Nothing. It settles on its own |
In Minuet | FirstIgnite is confident | Opens a read-only summary |
Verify match | Candidates found, something doesn't line up | Opens the reconcile view |
Not in Minuet with Add | Nothing matched | Opens the reconcile view |
Linked | Someone confirmed this by hand | Opens the summary |
Checking Minuet… only appears the first time FirstIgnite looks up a record. The result is cached, so later visits are instant.
If the badge doesn't appear at all, that isn't a match result. It means the CRM panel operation is off for your team, the record has too little to match on, or you're on a shared public project link, where FirstIgnite never touches your CRM.
A Linked badge is stronger than a matched one. Someone decided it, so it stays put rather than being re-evaluated.
The summary shows the matched Minuet contact or company, and View full profile in Minuet opens the complete record in Minuet.
An In Minuet badge with its Strong match pill and the three signals it matched on: email, name and company. The percentage appears because the email matched; a name-and-company match shows none
The read-only summary an In Minuet or Linked badge opens: the Minuet ID, title, company, department and email, with View full profile in Minuet, Re-reconcile and Create marketing target pinned along the bottom
Why a match needs verifying
FirstIgnite scores three signals for a person: email, name and company. For a company it scores two, domain and name. It always says which applied:
Email matches exactly.
Name and company match — but no email to confirm.
Name matches — no email or company to confirm.
A missing email doesn't demote a match on its own. If the name and company agree and there's no email to compare, FirstIgnite treats that as confident, and shows no percentage.
What produces Verify match is a disagreement:
The email matches but the name doesn't, often a shared mailbox like
info@on the Minuet record, or a contact who has moved on.The name matches but the company doesn't, which happens with the same name at two organisations, or a job change.
Each candidate carries a confidence pill reading Strong match, Possible match, Weak match or No match, sometimes with a percentage. Strong is what sits behind an In Minuet badge, and behind Auto-matched (strong) in a bulk send. Possible and Weak are what produce Verify match.
If two Minuet contacts share a name, FirstIgnite says so and asks you to pick.
A Possible match where the name agrees but the company differs. FirstIgnite shows both records side by side and asks you to decide
Reconciling a match
The reconcile view puts the FirstIgnite record beside Minuet's search results, with the reason for each candidate.
Open the badge.
Compare the candidates.
Pick the right record, or choose an outcome.
When more than one Minuet record matches, the extras are listed under Other candidates, each with No match and Pick this one beside it
The outcomes:
None of these are right. Search Minuet again. Try a different email, or search by company. For a company record, try its domain.
They're not in Minuet yet, or It's not in Minuet yet for a company. The record stays unlinked for now. To create the record, use the Not in Minuet badge instead (next section).
They're different people, or They're different companies. That leaves it unlinked and stops FirstIgnite suggesting those candidates for 30 days, then re-checks in case your Minuet data has changed.
The three outcomes at the bottom of the reconcile view: None of these are right, They're not in Minuet yet, They're different people
A few details about that last one. The badge doesn't disappear. It goes back to Not in Minuet so you keep a way in. A genuinely new strong match still breaks through before the 30 days are up. FirstIgnite holds back only the candidates you rejected. And if you later link one of them by hand, the suppression clears.
Search accepts a plain query or a specific field: email, name or company for people; name or domain for companies.
Creating a record in Minuet
From a Not in Minuet badge, the reconcile view opens straight into a create form. Review and edit the fields FirstIgnite has proposed, then confirm with Create & Link. FirstIgnite creates the Minuet record and links the FirstIgnite record to it in one step.
The create form. It lists what is about to happen — link the company, create the contact, link the two — above the fields you can edit, and notes that no Marketing Target is created here
For a contact you can edit name, title, department, specialty, email, address, website and description. For a company, name, type, address, phone, website, description, size, tax ID and the rest of the standard fields.
When a person's company is also missing, you choose Create company too or Skip — link contact only.
When the person's company is missing from Minuet as well, FirstIgnite offers Create company too or Skip — link contact only
Its own block in Comments. FirstIgnite writes an overview, experience, education and related detail into the record's Comments, marked as its own section and invisible in Minuet, so it can update that section later without touching anything your team writes.
A company record in Minuet with the Comments field showing the block FirstIgnite wrote: company overview, financials and markets, web and social, keywords
Linking to an existing company writes nothing. FirstIgnite records the link on its own side. No fields are updated and no comment block is added. (Logging an email against that contact later can add a secondary email address. See Logging FirstIgnite emails and activity to Minuet CRM.)
No undo. Minuet's API has no delete, so a record created by mistake has to be cleaned up in Minuet.
Creating and linking establishes who the record is. It does not create a Marketing Target.
Creating a Marketing Target from here
Once a contact is linked, the badge can also open a New marketing target form for that contact, with the company prefilled and a focus selector offering Technology, Marketing project or Patent. It's the same form as the one on a project's marketing panel, and it needs the Push marketing targets operation. See Creating Minuet CRM marketing targets in FirstIgnite.
If Send organizations & contacts is off, FirstIgnite replaces the create form with "Creating in Minuet is turned off" and a note that you can still link to an existing match. Linking never depends on that operation.
Agreements and activity on a linked record
Once a record is linked, its Minuet context appears alongside it.
Active agreements shows title, status, type, direction, parties and dates. "Active" here means not archived. An agreement whose term has ended still shows unless it's been archived in Minuet. FirstIgnite doesn't request or display financial detail: royalty rates, revenue, estimated values, payables, billing comments and the free-text summary all stay in Minuet. Nor does it show the signed date.
Recent Activity shows Minuet activity for that record. Filter by All, Outbound, Inbound or Notes, by 7 days, 30 days, 90 days or All time, and by author. Each entry opens in Minuet.
A linked record's Minuet context: Recent Activity with its type, period and author filters, a remark that can't be displayed because of legacy RTF formatting, and the Active agreements card below it
Minuet itself excludes remarks marked private from reports, so they never reach FirstIgnite, including ones your own team wrote.
Occasionally an old remark reads "This remark's content can't be displayed (legacy RTF formatting)." That's an old record stored in a format the API can't return cleanly. It's intact. Open it in Minuet.
The same applies to comments. If your team keeps notes in Minuet's legacy rich-text comment field, FirstIgnite doesn't read or display them, and never writes to that field. It uses the HTML comment field. FirstIgnite leaves existing rich-text content alone.
Syncing enrichment onto a linked record
With Contact enrichment sync on, you can push what FirstIgnite has learned about a person or company into their Minuet record.
Choose Sync to Minuet. FirstIgnite shows Review proposed changes before writing anything. Only its own block in the Comments field changes; your team's notes stay put. Confirm with Confirm & sync.
Review proposed changes, shown before anything is written. The note beside it reads "Only FirstIgnite's block changes — partner notes are preserved." The proposed text is blurred here
If nothing has changed since the last sync you'll see "Already up to date — no changes to sync." and no write happens.
If something isn't working, see Troubleshooting the Minuet integration.