Docs: bulk import notes for name field split and value matching (CRMAAS-3091)

[haleyserrano]

JIRA

CRMAAS-3091

Classification

• Type: UI / UX change (bulk import flow adds explanatory copy) + feature behavior change (field option/tag matching)
• Product impacted: Business App (this PR) — the same underlying CRM import behavior also affects Partner Center, so a companion PR is being opened there

Summary of documentation updates

Updated the existing CRM → Contacts article's import section (docusaurus/docs/business-app/crm/contacts/index.md) with two callouts:

1. A note explaining that contact names are stored as separate First name and Last name fields, so a CSV with a single "Name" column needs to be split into two columns before mapping.
2. A tip explaining that values mapped to fields with predefined options (e.g. Lifecycle stage) or to Tags are automatically matched to the closest defined option regardless of case.

Existing docs updated vs. new docs created

Updated existing documentation only — no new pages created. The ### Import contacts (and companies) section in the Contacts article already covered the import flow end-to-end, so the new guidance was added as two callouts alongside the existing warning/note callouts in that section.

Placement reasoning

The Contacts article (business-app/crm/contacts/index.md) is the single existing page that documents the bulk import flow for Business App end users. Adding the callouts directly after the existing import warning/note keeps all import caveats grouped together rather than splitting related guidance across pages.

Acceptance criteria coverage

• ✅ "The bulk import flow shows a note that contact names are stored as two fields... and that the CSV needs them as separate columns" → covered by the new :::info callout.
• ✅ "We will auto convert the import value to match with the field options defined" → covered by the new :::tip callout describing case-insensitive matching for field options and tags.

Figma / images

None provided or used. This ticket's Loom link documents behavior, not new UI, so no visual assets were needed for the text-only callout additions.

Skills used

• pre-push-validation — verified frontmatter and callout balance on the modified file.

Assumptions and limitations

• This story has no linked epic in JIRA and no gating/rollout tickets to check. The story's own status is Done with 4 merged PRs and 3/3 successful builds, so it was treated as shipped.
• The reviewer was selected as the ticket's assignee (Anshika Saini), matched to a GitHub collaborator on this repo via naming convention (asaini-lang), since no GitHub PRs were linked directly on the JIRA issue.

@ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code