feat(crm): allow contacts without a company domain

[selimshadyak47]

I'm importing attorney and law-firm data into Macro's CRM via the TypeScript SDK (packages/sdk) for my startup, DefenseBridge. The goal is a usable pipeline of firms and the individual attorneys at them.

Two SDK constraints block part of the data. macro.crm.createCompany({ domain, name }) rejects generic email-provider domains, and company.createContact({ email, name }) requires the contact's email domain to match the company's domain. The domain check lives in crates/crm/src/domain/generic_email_domains.rs. In my dataset of 4,009 attorney contacts across 2,878 firms, 317 contacts at 309 firms use personal addresses (gmail.com, yahoo.com, etc.). It's 8% of contacts, but they skew toward solo practitioners, which is the segment I'm targeting. None of them can exist in the CRM at all, even though they're the people I need in the pipeline.

Anyone selling to freelancers, consultants, or creators hits the same wall: the CRM currently models companies only, and a large share of independent professionals have no company domain.

Two possible directions:

• Personal contacts. Let a contact exist without a company, or auto-file personal addresses under a per-team "Individuals" bucket. Keeps the domain directory clean, but adds a second record type to the board and list views.
• Opt-in generic domains. A per-team setting that allows company creation from generic domains, off by default. Minimal schema change, but risks the problem the filter exists to prevent, where one generic domain becomes a company with thousands of unrelated contacts.

I'm not proposing changing the default domain-directory behavior for everyone.

Happy to implement whichever direction you'd prefer once there's alignment.

[modelpath-dev]

I will take this issue. Please assign it to me.

The problem seems to be with the domain validation in crates/crm/src/domain/generic_email_domains.rs. It blocks contacts with personal email domains. I would first review the domain check logic in this file. A small fix could be to add an option to bypass the domain check for personal contacts. This would allow contacts without a company domain to be added to the CRM. I will verify the fix by testing with a dataset that includes personal email addresses.

[selimshadyak47]

Appreciate the response. Let's see what direction the maintainers take first. A plain bypass would go against what the filter is there for in the first place. Once they decide, I'm happy to build it, and I have the data set ready to test against the issue.

[modelpath-dev]

Sounds good. I'll wait for the maintainers' input on the direction as well. Once we have their guidance, we can proceed with the implementation and testing. Thanks for having the dataset ready.

[whutchinson98]

Hi @selimshadyak47 Thanks for the issue. The current plan is to update CRM so you are allowed to manually create a CRM company using generic domains. There is a bit of investigation that is needed into how this would effect the automatic CRM detection as it may be domain specific atm. Once that is complete we will have someone work on it and get this done. :)

[modelpath-dev]

Got it, thanks for the update! I'll keep an eye out for any further details on the investigation and next steps.

[selimshadyak47]

@whutchinson98 Sounds good. Let me know how it progresses.

Selim S