Settings

Administrator sign-in

Sign in with the administrator account created for this pilot.

Client Company Setup

Your company

Upload and Download

Preview an ARIVE CSV or XLSX loan report, Fannie Mae 3.2 file, or MISMO 3.4 application file. Review the mapped fields, warnings and separate loan identities before importing. This does not enroll contacts, create milestone messages or activate billing.

Company legal documents

Your company’s agreements and retained document versions are private. You can download them whenever you need them.

Billing and payment methods

Private to your company’s billing owner. Card and bank details are entered securely with Stripe.

Billing is not configured.

Adding a bank account can require authorization and verification before it can be selected. The CRM stores masked details only.

A backup card is a saved preference. Automatic fallback charging is not enabled; a failed primary payment will not silently charge a different card.

Customer balance or invoice credit is separate from an ACH bank account.

CRM subscription

$49.99 USD per user per month. The first paid partial month and unused time at termination are prorated.

Email and optional AI usage

Standard email · Amazon SES

Prepaid standard email costs $1 per 1,000 recipient emails. An email sent to three recipients uses three recipient emails.

Optional AI allowance

Each prepaid monthly allowance unit costs $5. Renewal requires a reviewed purchase; there is no automatic recharge. Two units double the price and allowance. Allowance is measured in usage units, not minutes. Mid-cycle upgrades are prorated in the purchase review.

Saved usage purchases

Check an existing payment without creating a new checkout or charge. Uncertain purchases remain held for owner review.

Client Company Setup — email branding

Enter company information here once. Email Profiles uses this saved company setup.

Client Company Setup — ARIVE

Company details feed Email Profiles and remain editable in Client Company Setup. Company administrators can replace the private ARIVE credentials below.

ARIVE credentials

Email Profiles

Company details flow from Client Company Setup. User details and signatures flow from User Setup.

Edit Client Company Setup · Edit User Setup

User Setup

Your contact details and signature are saved for your user in this company.

Sending Hours and Time Zone

These are the master limits for all future email, SMS and workflow sending. Other schedules can narrow these hours, but cannot expand them.

Sending remains disabled in this pilot. You can save and check the rules without sending a message.

Sending and scheduler

Owner testing only. Customer sending is disabled. Scheduled checks run on Amazon, even when this browser is closed. The test queue below contains no contact or recipient.

Background scheduler

Company email limits

Only the CRM owner can change these limits. Amazon account limits and the master Sending Hours and Time Zone can further restrict sending.

Test background scheduling without email

Queue one synthetic test for 60 seconds from now. It checks routing without opening a mailbox, contacting a borrower, sending email or using prepaid email credit. The latest master sending rules still apply.

Queued and held tests

Amazon SES readiness

Bulk email credentials stay private to the CRM owner. These checks do not change subscriber billing or activate customer sending.

Appearance

Choose a display mode and your pipeline box colors. Changes preview immediately; save to keep them for this company.

Users and Roles

Your primary administrator is protected. Save a staff record first, then choose Send invitation when you are ready to give that person access.

These roles control access to the pilot’s Contacts, Pipeline, users and Settings. Billing is restricted to the primary company owner and stays locked until the platform owner activates it.

Company users

Add staff record

Gmail and Microsoft connections

Connect your own mailbox, then check that AWS can verify it. Open Email to read messages and prepare drafts. Individual Gmail sending requires separate permission, a final review and your Send click. Automatic workflow and campaign sending remains disabled.

Disconnect removes the connection from this pilot only. Your existing CRMs stay separate.

ARIVE — Zapier receiving

Each copied Zap uses its own private company receiving key. This shell accepts only records whose normalized mortgage loan officer name is Danny Hacker. Receiving a record never sends a message or starts a campaign.

Put the receiving key in the copied Zap’s x-crm-webhook-key header and company_e09434795b9747a0a1f9270acc8e7184 in x-crm-company-id. Keep the copied Zaps in this company’s Zapier folder.

Received events

This inbox shows received events and field mapping. Review the matching contacts and separate loan cards in Contacts and Pipeline. Receiving does not send messages or activate workflows.

What you can try now

Save the company name, contact email, and time zone. Reload the page or sign out and back in to confirm the saved values remain.

Use the sections above to review and save your pilot settings. Billing stays locked until the platform owner activates this company.

Owner support access

Choose whether the named CRM owner can inspect maintenance status and apply reviewed software updates. This never permits sending, billing, viewing credentials or editing your customer records.

Supervised access pauses when this page is hidden, closed or disconnected. Revoking blocks new maintenance steps; an update already submitted to AWS must finish or be reviewed for rollback.

Allow the named owner to view CRM records

This is separate from software-maintenance permission. It permits read-only contacts, linked loans, notes, tasks and redacted company settings. It does not permit sending, editing, billing, downloading records, credentials or signing in as you.

Each owner session lasts at most 10 minutes and rechecks this permission on every read. Supervised access is held after the subscriber heartbeat becomes stale (at most 90 seconds without an update). Revocation blocks subsequent reads; information already delivered cannot be recalled.