Unificar
← Documentation

Glossary

Short definitions for Unificar. If you know Follow Up Boss, many names match — this list only covers what we ship. For setup order, see the Team onboarding checklist.

People & pipeline

| Term | Meaning in Unificar | |------|---------------------| | Person | A contact / lead record (/people/[id]). FUB often says “lead.” | | People | Your book of business — lists, filters, bulk actions. People & lists | | Stage | Where the relationship is in the pipeline (one stage per person). Managed under Admin → Stages. | | Source | Where the person came from (Zillow, referral, website, …). Used in Lead Flow and reporting. | | Tag | Flexible labels; a person can have many. Admin → Tags. | | Smart list | A saved filter set on People (stage, source, and more). | | Custom field | Extra person fields your team defines. Admin → Custom Fields. | | Deal | A pipeline / transaction card linked to a person. Calendar & Deals |

Assignment & routing

| Term | Meaning in Unificar | |------|---------------------| | Team | The account / tenant (solo or multi-agent). Created at register; data is isolated by team. | | Company | Profile for that team (name, timezone, phone, address, website) — Admin → Company. Not a separate entity. | | Admin / Agent | Roles on a team membership. Admins get Admin in the avatar menu. | | Lead Flow | Per-source rules: who gets new people and which Action Plan starts. Admin → Lead Flow | | Group | A pool of agents for round-robin or first-to-claim assignment. Admin → Groups | | Pond | Shared queue of people agents can claim. Ponds | | Pause leads | Member flag — stop receiving new Lead Flow / round-robin assignments. |

Follow-up & automation

| Term | Meaning in Unificar | |------|---------------------| | Action Plan | Multi-day sequence (tasks, email, SMS steps). Enroll from a person or Lead Flow. Admin → Action Plans | | Automation | Runner + event triggers (person_created, tag_added, no_contact_days, pond_claim) and stage automations. Admin → Automations | | Task | A to-do, often tied to a person. Inbox & Tasks | | Template | Reusable email or text with merge fields like {{first_name}}. Admin → Email / Text Templates |

Communication

| Term | Meaning in Unificar | |------|---------------------| | Inbox | Attention queue for leads, tasks, and logged/sent email/text/call threads — not a connected Gmail/Outlook mailbox. Inbox & Tasks | | Log call | Save call notes + outcome on the person (or in Inbox). Dialing is click-to-call (tel:), not a CRM dialer. | | Send vs log only | Composer can deliver via configured channels or only record the activity. | | Channels | Configured email/SMS providers (console / Resend / Twilio). Admin → Channels |

Day-to-day surfaces

| Term | Meaning in Unificar | |------|---------------------| | My Day | Today’s people and tasks. My Day | | Dashboard | Team KPI snapshot at /. Dashboard | | Activity | Team activity feed. | | Reporting | Charts + CSV for pipeline, sources, activity, deals. | | Appointment | Calendar event / meeting on a person. Kinds configured under Admin → Appointments. |

Integrations (what we have)

| Term | Meaning in Unificar | |------|---------------------| | API key | Scoped key for inbound leads (POST /public/leads) and /public/v1/…. Admin → API Keys | | Webhook | Outbound events with HMAC + delivery log. Admin → Webhooks | | Import | CSV file or paste into the team. Admin → Import |

Not Unificar terms (FUB-only — skip)

These FUB glossary ideas are not product features here: connected email, company/shared phone numbers, dialer / call recording, batch email blasts, collaborators, Lender/ISA/Owner roles, IDX marketplace, Inbox lead processing from a synced mailbox.