Brokerage Settings Reference

This reference describes all fields and options available in the brokerage administration panel.

Broker vs Admin Access

Brokers can view and suggest changes to their brokerage settings, but only administrators can directly save changes. When logged in as a broker, changes are queued for admin approval.

Organization

The brokerage editor contains eight tabs:

General

Basic info, licensing, and address

Branding

Logo, colors, hero section, and navigation

Features

Toggle site features and lead routing

Map

Set service area and map defaults

Contacts

Manage broker contacts

Domains

Configure white-label domains

Content

External blog content sync

Data Feeds

MLS data source connections

---

General Tab

Basic Information

Field	Type	Required	Description
Brokerage Name	Text	Yes	Official brokerage name
Tagline	Text	No	Short marketing tagline displayed on the website
Description	Long text	No	Full marketing description for your brokerage
Website	URL	No	Brokerage’s external website URL

Licensing & Legal

Field	Type	Required	Description
License Type	Text	No	Type of real estate license (e.g., DRE, MLO)
License Number	Text	No	Official license number

Office Address

Complete physical address including:

• Street Address (text)
• City (text)
• State (text)
• ZIP Code (text)
• Country (text)

---

Branding Tab

Social Media

Platform	Field Type	Description
Facebook	URL	Facebook page URL
Twitter/X	URL	Twitter/X profile URL
LinkedIn	URL	LinkedIn company page URL
Instagram	URL	Instagram profile URL
Pinterest	URL	Pinterest profile URL
YouTube	URL	YouTube channel URL

Logo & Colors

Setting	Type	Format	Description
Brokerage Logo	Image upload	PNG, JPG, SVG	Wide format logo (recommended 2:1 ratio, minimum 600x300px)
Primary Color	Color picker	Hex code	Brand color used throughout the site
Franchise Affiliation	Dropdown	Predefined list	Franchise brand (e.g., RE/MAX, Keller Williams)

Hero Section

Field	Type	Description
Headline	Text	Main text displayed prominently on homepage
Subtitle	Text	Supporting text below the headline
Search Examples	Multi-line text	Example queries that rotate in the search bar (one per line)

Navigation

Both header and footer navigation support:

Property	Type	Description
Label	Text	Display text for the link
URL	Text	URL path (relative or absolute)
Visible	Boolean	Toggle visibility without deleting
Order	Drag-to-reorder	Visual reordering of menu items

---

Features Tab

Specializations

Feature	Type	Description
VA Loans	Boolean	Indicates specialization in VA loan transactions
Military Specialist	Boolean	Indicates specialized service for military personnel and veterans

Feature Flags

Feature	Type	Default	Description
Semantic Search	Boolean	Enabled	Natural language property search
Map Search	Boolean	Enabled	Interactive map-based property browsing
Favorites	Boolean	Enabled	Allow users to save favorite properties
Contact Form	Boolean	Enabled	Property inquiry and tour request forms
Virtual Tours	Boolean	Enabled	3D virtual tour integration (Matterport, etc.)
Mortgage Calculator	Boolean	Enabled	Built-in mortgage payment estimator

Lead Routing

Routing Mode (dropdown):

• primary_only — All leads go to the designated primary agent
• round_robin — Distribute leads evenly among eligible agents (rotation persists across redeploys)
• subject_based — Match leads to agents based on the inquiry subject and per-agent expertise rules
• random — Pick a random eligible agent (rarely the right pick — useful only for A/B testing)
• semantic — Match the inquiry text against each agent’s match criteria via semantic similarity

Options (set via lead_routing_rules JSON):

• use_semantic_filter — Pre-filter the agent pool to the top semantic matches before applying round_robin, subject_based, or random. Hybrid routing — broadens the eligible pool with relevance ranking, then picks via your chosen distribution rule.
• semantic_top_n — How many agents to keep after the semantic pre-filter (default: 3)

Fallback Mode (lead_fallback_mode):

• primary_agent — Assign unmatched leads to the designated primary agent
• unassigned — Leave unmatched leads without an agent; the broker reviews manually

Note

Only agents with “Lead Recipient” enabled in their profile receive leads. For a deeper walkthrough of each mode and when to pick which, see Routing Modes.

Response and Follow-up

Below the routing controls on the same card. Leave a field empty to use the platform default.

Field	Type	Default	Description
Response target (minutes) (lead_sla_target_seconds, stored in seconds)	Integer (1-1440)	5	How long an agent has to log a first contact attempt on a new lead. Drives the countdown on the board, the detail page and the dashboard.
Archive after no response (days) (lead_timeout_no_response_days)	Integer (1-3650)	21	A CONTACTING lead with no activity of any kind for this long is archived by Scribe with timeout_no_response.
Archive after no progress (days) (lead_timeout_no_progress_days)	Integer (1-3650)	180	A QUALIFIED lead idle for this long is archived by Scribe with timeout_no_progress. Committed and in-contract leads are never timed out.
Email the agent when the response window is missed (lead_sla_alerts_enabled)	Boolean	Enabled	One email per lead to the assigned agent, or to the brokerage’s brokers when nobody is assigned. The countdown stays visible either way. Off means the reminder and the escalation below are off as well.
Remind again after (minutes) (lead_sla_reminder_minutes)	Integer (1-10080)	30	Counted from the breach email. One more email to the same people if no contact attempt has been logged.
Escalate to brokers after (minutes) (lead_sla_escalate_minutes)	Integer (1-10080)	120	Counted from when the lead arrived, and only once the response target has closed. Emails the brokerage’s brokers and owner naming the agent who has not responded, and writes an Escalated to brokers row on the lead’s timeline.
Reassign the lead when it escalates (lead_sla_auto_reassign)	Boolean	Off	At escalation, routes the lead again through the routing mode above with the current agent left out. The new agent gets the usual assignment email and the timeline records the move with the reason sla_escalation. If nobody else is eligible the lead stays put and the escalation email says so.
Final escalation after (minutes) (lead_sla_final_escalate_minutes)	Integer (1-10080)	1440	Counted from when the lead arrived, and only after the escalation above. Emails the brokers and owner one last time, naming whoever has the lead now and whether reassignment already moved it, and writes an Escalated again to brokers row. With reassignment on, routes the lead once more leaving out every agent who has had it (reason sla_final_escalation).
Text message alerts (lead_sla_sms_enabled)	Boolean	Off	Every rung also sends a short text: to the agent’s mobile number (office line as a fallback), and to brokers and the owner at the phone on their broker contact. Needs a Twilio account on the brokerage (below) or on the platform; the form says so when there is neither. See configure SMS alerts.
Browser push alerts (lead_sla_push_enabled)	Boolean	On	Every rung also sends a browser push to the same people, when the platform can send push.
Twilio Account SID (twilio_account_sid)	String	Empty	The brokerage’s own Twilio account. With all three Twilio fields set, texts go out from this account instead of the platform’s.
Twilio Auth token (twilio_auth_token)	Secret	Empty	Write-only. Stored encrypted; the API only reports twilio_auth_token_set. Send an empty string to remove it.
Twilio From number (twilio_from_number)	Phone	Empty	The SMS-capable number texts are sent from. Normalized to +1…; an unsendable number is refused.
Book a follow-up automatically after each contact (follow_up_auto_schedule)	Boolean	On	Logging a contact attempt or a lead response books the next follow-up at the default interval unless the agent picks a date or skips it.
Follow-up default interval (follow_up_default_days)	Integer, 1 to 365	3	Days after a contact for the automatic follow-up, and the suggestion when an agent schedules one by hand.

Agents have one switch of their own on the agent profile, Text me lead alerts (alerts_sms_enabled, on by default), next to the mobile phone field. Off means the brokerage’s text messages skip that agent; email and push are unaffected.

The checks run inside the platform about once a minute. Archived leads are not deleted; Re-engage brings them back to CONTACTING, and the timeline row shows how long the lead had been idle when Scribe archived it.

---

Map Tab

Map Configuration

Field	Type	Description
Center Point Latitude	Decimal	Latitude coordinate for default map center
Center Point Longitude	Decimal	Longitude coordinate for default map center
Default Zoom Level	Integer (1-18)	Zoom level when map loads
Base Map	Dropdown	street or satellite

Service Area Bounds

Boundary	Type	Description
North	Decimal	Northern latitude boundary
South	Decimal	Southern latitude boundary
East	Decimal	Eastern longitude boundary
West	Decimal	Western longitude boundary

Note

Properties outside service area bounds are excluded from search results.

---

Contacts Tab

Broker Contact Fields

Field	Type	Required	Description
Name	Text	Yes	Contact’s full name
Photo	Image upload	No	Profile photo (JPG, PNG)
Email	Email	Yes	Email address
Phone	Phone	No	Phone number
License Type	Text	No	Type of license held
License Number	Text	No	License number
Primary	Boolean	No	Designates this contact as primary (only one allowed)

---

Domains Tab

Domain Properties

Property	Type	Description
Domain Name	Text	Fully qualified domain name
Verification Status	Status	verified or unverified
DNS Provider	Detected	Auto-detected registrar
Primary	Boolean	Canonical domain designation (only one allowed)

DNS Configuration

Required DNS record:

• Type: CNAME
• Value: idx.l.supported.systems

---

Content Tab

Git Repository Configuration

Field	Type	Required	Description
Git Repository URL	URL	Yes	HTTPS or SSH URL to content repository
Branch	Text	Yes	Git branch to sync from (default: main)
Content Path	Text	Yes	Directory containing posts (default: posts)
Authentication Method	Dropdown	Yes	ssh_key or access_token
SSH Private Key	Textarea	Conditional	Deploy key with read access (required if SSH)
Access Token	Text	Conditional	Personal access token (required if token auth)
Enable Content Sync	Boolean	No	Toggle automatic sync during builds

Sync Status (Read-only)

Field	Type	Description
Last Synced	Timestamp	Date and time of last successful sync
Commit Hash	Text	Git commit SHA that was synced

---

Data Feeds Tab

Feed Properties

Field	Type	Required	Description
Feed Name	Text	Yes	Descriptive identifier
Feed Type	Dropdown	Yes	mlsgrid, reso_web_api, or rets
Enabled	Boolean	Yes	Toggle to enable/disable syncing

MLSGrid Feed Type

Field	Type	Required	Description
Access Token	Text	Yes	MLSGrid API access token
Originating System Name	Text	Yes	MLS identifier (e.g., imls, sdar)
Base URL	URL	No	API endpoint (default: https://api.mlsgrid.com/v2)

RESO Web API Feed Type

Field	Type	Required	Description
Web API URL	URL	Yes	MLS’s API endpoint
Server Token	Text	Yes	Authentication token
Dataset ID	Text	Yes	Dataset identifier (usually MLS)
Client ID	Text	No	OAuth client ID
Client Secret	Text	No	OAuth client secret
Browser Token	Text	No	Token for browser-based requests
User-Agent	Text	No	Custom user-agent string

RETS Feed Type

Field	Type	Required	Description
RETS Login URL	URL	Yes	RETS server URL
Username	Text	Yes	RETS username
Password	Password	Yes	RETS password
User-Agent	Text	No	Custom user-agent string
User-Agent Password	Password	No	Password component for user-agent auth

Feed Status (Read-only)

Field	Type	Description
Last Synced	Timestamp	Date and time of last sync or “Never synced”
Test Status	Status	Result of last connection test

---

Metadata (Read-only)

Field	Type	Description
Created At	Timestamp	When the brokerage record was created
Updated At	Timestamp	When the brokerage was last modified