While every business needs a name and an email address, the data that really matters is often unique to your industry. Custom Lead Fields allow you to transform Myra from a generic CRM into a tailored database that matches your exact operational vocabulary.
Available Field Types
When creating a new field in Settings → Lead Fields, you can choose from several data types to ensure your data is clean and actionable:
- Text & Long Text: For names, notes, and general descriptions.
- Number: For quantities, ages, or scores. (Allows for "Greater than/Less than" filtering).
- Currency ($): Specifically formatted for British Dollars. Used in ROI and Revenue reports.
- Dropdown & Multi-Select: Perfect for fixed options like "Service Type" or "Lead Source." This prevents "Tag Bloat" and ensures consistent reporting.
- Date & DateTime: For birthdays, project deadlines, or last-service dates.
- Checkbox: For simple Yes/No questions (e.g., "Marketing Opt-in").
- File Upload: Allow leads or staff to attach PDFs, images, or documents directly to the contact record.
- URL: For LinkedIn profiles, company websites, or portfolio links.
Organizing with Field Groups
As your CRM grows, having 50 fields in a single list becomes overwhelming. Field Groups allow you to categorize your data:
- Basic Info: Name, Email, Phone, Address.
- Qualifying Data: Budget, Project Timeline, Company Size.
- Technical Specs: (Industry specific) e.g., Vehicle VIN, Property Type, or Insurance Policy Number.
- Internal Use: Commission rate, Account Manager notes, Internal ID.
Pro Tip: You can set entire groups to be "collapsed" by default, keeping the contact interface clean and focused.
Advanced Field Logic
Conditional Visibility
Make your CRM "smart" by only showing fields when they are relevant. Example: Only show the "Parking Requirements" field if the "Event Type" dropdown is set to "In-Person." This reduces clutter and ensures your team only fills out what is necessary.
Validation Rules
Prevent "dirty data" from entering your system.
- Required Fields: Mark a field as required so a contact cannot be saved (or a form cannot be submitted) without it.
- RegEx Validation: Ensure phone numbers follow a specific format or that a "VAT Number" field contains the correct number of digits.
Mapping & External Data
Custom fields are the "landing spots" for data coming from outside Myra.
- Form Mapping: When you build a form, you "map" each question to a Lead Field.
- Inbound Webhooks: If you use Zapier or a custom API to push leads into the platform, you'll use the "Internal Name" of your custom fields to ensure the data lands in the right place.
Best Practices
- Use Dropdowns over Text: Whenever possible, use a dropdown menu. It's much easier to filter a segment by "Industry: Construction" than to search for "Construction," "Building," "Contractor," and "Builder."
- Internal Names Matter: When creating a field, the "Internal Name" (e.g.,
project_budget) is used by the API and Automations. Keep these lowercase and use underscores instead of spaces. - Limit PII: Be mindful of storing sensitive Personal Identifiable Information (PII). Only create fields for data you actually need to run your business.
Frequently Asked Questions
Can I change a field type later? No. Once a field is created as a "Number," it cannot be changed to "Text." You would need to create a new field and migrate the data. This is to protect the integrity of your reports and automations.
Do custom fields show up on the Mobile App? Yes. All custom fields and groups are fully accessible and editable via the Myra mobile app.
Can I use these fields in my email templates? Absolutely. Every custom field is available as a "Merge Tag" or "Token." You can send an email that says, "Hi {{contact.first_name}}, I see your budget is {{contact.budget}}..."