Customize SalesDrone

Default: From Google

Displays the verified Google identity and its profile photo, with initials as a fallback. These details are not edited in SalesDrone.

Change the source profile in Google, then sign in again.

Default: Granted by an administrator

Shows whether this identity has live membership. Signing in alone does not grant lead access; unapproved identities see synthetic demo data.

Permissions are enforced server-side, including direct links and API requests.

Default: System

Choose System, Light or Dark. System follows the device preference. The top-right theme control offers a quick switch. The quick switch shows sun and moon icons in a compact pill; a solid indicator marks the active mode. Tap or use Enter/Space to switch. Reduced motion removes the indicator transition.

Saved appearance applies to your account; the browser also remembers a local fallback. Demo appearance is local. On desktop, lead blade width is adjusted directly in Leads using its left edge (double-click resets it); expand opens a dedicated lead page. That width is remembered only in the current browser, separately from account preferences; double-click the edge to reset it.

Default: Standard (Google Sans headings and Manrope text)

Choose Standard, Inter, Source Sans 3 or Lora for your own interface. A sample previews the draft selection; the workspace changes after a successful Save changes. Font files are self-hosted, with no runtime Google Fonts request.

Saved on your own account through PATCH /me and returned by GET /me. Older clients that omit fontStyle preserve it. Book mode uses its own serif stack and restores your selected font when disabled. Branding, phone numbers and technical code retain their established fonts. Other users are unaffected. Demo choices are a guarded browser-local fallback.

Example: Choose Inter for a compact interface or Lora for an editorial serif style, inspect the sample, then save. Standard restores the original pairing.

Default: 100% (Standard)

Choose 85%, 90%, 100%, 110% or 125% for your own workspace on phones, tablets and desktops. Save changes applies the preference on the current device and future signed-in sessions. Default is 100%. Smaller zoom preserves usable touch targets; it does not disable browser or pinch zoom.

Stored on your account through GET/PATCH /me; other members are unaffected. Choose 100% to reset. Browser zoom and pinch zoom remain available. Older clients preserve an omitted displayScale; missing or unsupported values fall back to 100%. Demo choices stay browser-local and cannot override an authenticated member preference.

Example: On a phone choose 90% to fit more content, or 110% for larger text, then save. Return to 100% to reset. Additional desktop columns still scroll within the table.

Default: Off

A personal reading style with warm paper surfaces and serif fonts throughout headings, navigation, tables, forms, buttons and chart labels. Dark mode uses charcoal paper. Phone numbers remain monospace. This is a visual style, not physical e-ink or an offline reader.

Select Book mode and save preferences. Your account stores bookMode; other members are unaffected. Light/Dark/System and the quick light/dark toggle remain independent. Omitted bookMode in older API clients preserves the saved value; missing preferences default off. Demo/guest preference is a guarded local fallback. Responsive type-size roles match the standard UI while keeping the Book serif family; this is a web adaptation, not native Dynamic Type. Shared typography roles and responsive layouts apply across phones, tablets, laptops and desktops; font families remain serif in Book mode.

Example: Enable Book mode with Light for ivory paper, then use the top-right toggle for warm night reading. Turn Book mode off and save to restore the standard workspace.

Default: Asia/Kolkata for live accounts

Use an IANA timezone, such as Asia/Kolkata or Europe/London. It controls displayed dates, dashboard calendar boundaries and automatic reminder interpretation.

Save preferences. Manual reminder forms label the device timezone they use; already scheduled instants do not move.

Example: Set Europe/London before adding a note saying “tomorrow morning”.

Default: Automatic: first available category field

Set directly on the Today dashboard. Choose Enquiry status, Sales stage, source, sector, location or an active custom text/dropdown field. Sales stage remains explicitly selectable for analytics even when hidden from forms. Other hidden/retired fields are excluded; Automatic keeps its visible-field fallback.

Personal account preference through GET/PATCH /me and GET /dashboard. Changes apply immediately to the two lead distribution charts. Partial/older preference saves preserve the choice. Workflow stages, KPI definitions and AI brief inputs remain unchanged. Show up to 20 groups plus Other values; aggregates and values exceeding filter limits have no direct drill-through. Demo saves are browser-local. Headings, descriptions and notes follow the effective configured field label.

Example: Hide Sales stage in Manage fields, then leave Automatic or choose Enquiry status on Today. A field that later disappears falls back with a notice; choose another field to replace the saved selection.

Default: Not registered until enabled

Requests browser notification permission and registers this device for Firebase Cloud Messaging. In-app notifications remain available even when push is blocked.

Allow the browser prompt. On supported iPhone/iPad versions, install the web app on the Home Screen and enable it there. Delivery can be delayed by the OS.

Default: On demand

Sends a synthetic readiness notification to the selected registered device.

FCM acceptance does not prove the device displayed it. Check the browser permission and OS settings if it is absent.

Default: Enabled registrations remain until revoked or invalidated

Stops future push delivery to that registration. Revoking this browser also deletes its local messaging registration.

In-app reminders and notifications are retained. The notification bell lets you mark inbox items read or unread.

Default: No archived leads until records are archived

Lists archived leads in Settings in 30-record pages with contact details and stage. Only permitted leads are returned, including when opening direct links. Archived leads stay outside the active pipeline and cancelled reminders remain cancelled.

Refresh reloads the first page. Load more follows a signed, access-bound cursor. View lead record opens without restoring. Restore lead confirms and returns a permitted record to the active list, retains suppression and shared contacts, and never reschedules cancelled outreach. Administrative tasks retain state. No permanent deletion here.

Example: Archive a lead from its record, then open Settings > Archives. Older archives display Date not recorded instead of inventing an archive date.

Default: On

Lets members with lead access export matching lead fields and selected columns from Leads → Export Excel. Admins are also subject to this switch.

Turning it off blocks the report API as well as hiding the action. It does not prevent copying data a person is already authorized to read. PAT reports require leads:export.

Example: Filter Sector equals MEP, choose phone and company, then export all matching pages.

Default: On

Caps every non-admin at assigned scope, including members whose configured scope is All leads. Admins retain their existing scope.

Applies to lists, direct links, reports, dashboards and reminder/notification eligibility on the next API request. Existing UI sessions recheck on focus/every minute. Off restores configured member scope; it does not broaden an assigned member.

Example: Keep on for SDRs working separate portfolios.

Default: Standard enquiry labels

Rename display names for existing lead fields. The internal API keys, stored values, field types and validation semantics stay fixed. Names must be nonempty, distinct and no more than 80 characters.

Shared forms, table/filter labels and report headers use the configured names after refresh.

Example: Rename Sector to Business segment without changing the zone API key.

Default: Visible

Use the trash icon to remove standard fields from enquiry entry and configurable columns, filters and new reports where applicable. Use the restore icon to bring them back. Customer name and Enquiry date stay required; keep Phone number or Email available. A disabled delete control explains the minimum requirement.

Existing records and values are preserved. This is workspace-wide presentation configuration, not authorization or removal of sales-stage, call, assignment, suppression or review workflows. Removing Country code uses the first configured country code for new manual enquiries; existing contacts retain their country code. A hidden Sales stage defaults new enquiries to New.

Example: Remove Phone number when you collect Email instead, or remove Sector and restore it later.

Default: No custom fields

Add up to 30 custom fields: text, long text, number, date, dropdown or checkbox fields with stable cf_ identifiers. Choose a unique label and optionally make the value required. Existing IDs/types cannot be changed or reused after retirement.

Required rules apply to new manual entries or explicit custom-value edits, not unrelated edits to legacy records. The first-sheet importer currently maps standard enquiry fields, not arbitrary custom-field columns.

Example: Add a dropdown named Material category with Cement, Aggregates and Blocks.

Default: Provided when creating the dropdown

A custom dropdown needs at least one distinct nonempty choice. Choice labels are bounded and case-normalized duplicates are rejected.

Removing a choice preserves unchanged historical values but prevents new use of that retired value.

Default: Active

Remove an unused custom field from new-entry controls without erasing historical lead values.

Retired IDs cannot be reused. Create a new field for a different data type instead of rewriting existing values.

Default: Direct enquiry, Website, Referral, Exhibition, Social media, Other

Maintain where enquiries originate.

Used in lead capture, filters and imports. Existing historical values remain readable.

Default: No preset list

Add city/location suggestions appropriate to the business.

The same configured options are reused by shared controls; old records are preserved.

Default: No preset list

Add industry, territory or sector choices matching your sales process.

The underlying key remains zone even if you rename its label in Lead fields.

Default: Call/WA done, Samples sent, Won/Order placed, Quoted

Maintain spreadsheet enquiry status choices separately from sales stages and call outcomes.

Historical enquiry status is not automatically treated as a stage transition.

Default: New, Working, Qualified, Meeting booked, Nurture, Disqualified, Won

Add sales stages and arrange the sequence used by forms, journeys and dashboard funnel.

Protected baseline workflow values are retained. A current-stage funnel is not a historic conversion rate.

Default: Standard connected / unanswered call outcomes

Customize the available results of a phone call while retaining protected workflow outcomes.

Changing choices does not rewrite old call records.

Default: None, Interested, Not interested, Callback requested, Do not contact

Describe the contact’s response separately from the technical call outcome.

Do not contact is protected and suppresses outreach; renaming a field does not remove suppression rules.

Default: +91, +1, +44, +971, +65, +61

Maintain country dialing prefixes used in contact entry.

Preserves original phone input and normalized duplicate checks. Each choice list supports up to 100 distinct values of up to 100 characters.

Default: When I ask (manual)

Manual shows a compact Get insights / Refresh insights action. When the dashboard opens requests insights once per visit and hides the button.

Recent matching cached briefs are reused. Chart refreshes do not regenerate. Automatic mode can use more model requests; failures do not loop.

Default: Default grounded sales briefing

Customize focus, tone and language, up to 4,000 characters. Blank text uses the displayed default; Use default clears custom guidance, and Save preferences applies it.

Applies to dashboard prose, not scoring factors or automatic reminder interpretation. Guidance cannot expand access, invent evidence or contact leads. Changes invalidate cached/stale in-flight briefs.

Example: Use concise Tamil bullets, focusing first on overdue callbacks and missing qualification context.

Default: On

New lead notes and call comments are analyzed by Gemini for a clear dated next step. Conditional, conflicting or vague instructions need review.

Disabling stops pending analysis and new automatic extraction; it does not delete existing tasks. Manual tasks/edits take priority. Imported historical comments do not schedule new reminders.

Default: 10:00

Time of day used when an inferred dated follow-up has no explicit time.

Uses your display timezone; exact written times take precedence.

Example: “Call tomorrow” uses 10:00 unless you choose another default.

Default: Seven days after the note

Choose seven days after the note or next Monday for ambiguous next-week wording.

Only ambiguous relative wording uses this preference; named dates/weekdays remain explicit.

Default: Off

Moves qualifying relative dates without an explicit time from a weekend to the next working day.

Exact dates and named weekdays are kept as written; this is not a configurable holiday calendar.

Default: On

Controls background evidence-based qualification under the workspace model.

Off disables scoring; it does not fabricate zero scores or delete historical lead data.

Default: Commercial construction / wholesale defaults

Define what counts as Fit, Intent or a Red flag. Gemini must cite recorded evidence rather than guess. Conditions are 10–600 characters; labels up to 80; up to 30 factors.

Condition/factor changes require fresh evidence analysis. Missing evidence remains unknown. This is sales prioritization, not a credit, licensing or safety verification.

Example: Add an Intent factor for a documented active RFQ.

Default: Default positive weights and red-flag penalties

Give enabled factors integer weights from 1 to 100, or disable an irrelevant factor. Keep at least one enabled Fit or Intent factor when scoring is on.

Positive matches are normalized against enabled positive weights; red flags subtract points; the result is clamped to 0–100. Weight-only edits can recalculate without new extraction.

Default: Default factor set

Add business-specific signals or remove irrelevant ones. Stable factor identity ties evidence to the model.

Background scans are bounded; bulk changes are not guaranteed to finish immediately. Inspect evidence coverage, not just the score.

Default: Empty; Setup required

Choose the current Admin-configured stages representing converted leads.

Exact current counts use these choices. Calendar-month counts use recorded entries into this group; each lead counts at most once per requested month. Creation/import and moves within this group do not count.

Default: Empty; Setup required

Choose the stages representing failed enquiries. Converted and failed groups must be disjoint.

Current failed counts use the full accessible active cohort. Failure themes use only retrieved, source-verified evidence from currently failed leads.

Default: Empty; no archive suggestions

Choose stages eligible for manual archive review.

A finding additionally requires recorded last contact older than the threshold and no pending task. No automatic archive, merge, deletion or outreach.

Default: Not configured

Choose 1–3650 days since last recorded contact.

A missing last-contact date does not establish inactivity. Age, low scores or shared phone numbers alone do not create archive candidates.

Default: Asia/Kolkata

Choose a valid IANA timezone for calendar conversions and Assistant reminder periods. Weeks run Monday through Sunday.

Monthly windows include the first calendar day and exclude the first day of the following month. February, leap years and timezone boundaries follow the calendar.

Default: Off

Opt in to a Gemini embedding backfill and incremental private search index. Existing server-side Gemini credentials are reused; no browser secret.

Enabling queues a bounded initial scan. Source edits atomically queue updates. Retrieval uses Firestore vectors with ACL prefilters and current source checks. Counts work independently of indexing. Index processing is bounded and may lag; failed jobs can be retried by an Admin rebuild.

Default: Provided on creation

A descriptive name of 1–80 characters helps identify an integration.

Names are metadata, not secrets or unique identifiers.

Default: Explicit selection required

Select only needed data operations. Scopes intersect the current owner’s capabilities and effective lead scope. Read leads and Export leads are separate. Batch editing has its own leads:bulk-edit scope. Lead files use attachments:read and attachments:write; old tokens do not gain these scopes automatically. Reassignment in a batch also requires assignments:write. Read-only MCP tokens can select team:read and people:read for Admin Team reports and the minimal id/name/active directory. Existing tokens gain no scopes automatically. These scopes do not grant member administration. tasks:read also reads shared tasks on an accessible lead; unrelated personal reminders remain private.

Tokens cannot manage people, workspace settings, devices, other tokens or AI generation. The live Swagger portal lists each route’s scope. See the generated scope catalog below.

Default: 30 days

Choose 7, 30 or 90 days. Up to 20 active tokens are allowed per owner.

Expiry and scopes are immutable; issue a replacement to change them.

Default: Shown once

Save the secret directly in your integration’s secret manager. SalesDrone stores a hash and cannot recover the full token later.

Never put it in URLs, screenshots, code or documentation. A lost creation response requires revoking its metadata and generating a replacement.

Default: Active until expiry/revocation

Stops subsequent authorization using that credential.

Already completed operations are not undone. Demoting/suspending the owner also blocks access.

Default: Same-origin /api/docs

Inspect request schemas, permissions and examples. Trying a write request changes real records.

Authorization stays in tab memory. Clear it when finished, especially on shared devices.

Default: No access until granted and accepted

Invite the intended Google account. Invitations expire after seven days and can be revoked.

The invitation binds to the verified identity that accepts it. Merely signing in does not grant live data.

Default: Viewer or SDR chosen for each grant

Viewer can read leads. SDR can also create/edit leads, record activity and manage tasks. Administrative capabilities are reserved for protected administrators. Lead editors may batch edit permitted records and upload/remove their lead files; readers may list/download permitted Ready files. Effective assigned-only policy applies to files as well. Admins can open Team insights and read member workload/authored activity within current lead scope. Team defaults to a 30-day UTC window, with 7/90-day alternatives; this is a local page selection and is not a grantable SDR capability. Active membership is distinct from online status. No PAT access or personal reminder visibility is added.

This screen does not promote other users to Admin or edit protected bootstrap admins.

Default: Assigned

Choose Assigned or All leads for a member. The workspace assigned-only cap still limits non-admins when enabled.

Changing scope applies server-side; old cursors/cached context cannot grant broader access.

Default: Role preset unless customized

Fine-tune non-administrative actions while retaining lead-read access. Lead readers can view shared lead tasks and responsibility on Tasks and inside the lead; lead editors can complete or reschedule Pending shared work without tasks:write. Personal reminders and delivery remain private. Import history, import writes and shared-import access can be granted separately; writes/sharing require import history permission. Lead create/edit permissions and effective lead scope still apply to import execution.

Removing a capability blocks subsequent relevant operations. UI visibility alone is not authorization.

Default: Active after valid acceptance

Disable a member’s live workspace access without deleting their historical work.

Current API requests, token checks and worker delivery eligibility use active membership. Re-enabling restores only the configured role/scope/capabilities.

Default: Off for Viewer/SDR; available to existing import-capable Admins

Grant imports:read to view the member’s import jobs and permission-filtered row results.

Read-only access does not allow uploads, review decisions, commits or deletion. Applies on the next server request after an Admin saves permissions.

Example: Grant shared history to a reviewer; grant write access only when they should execute imports.

Default: Off for Viewer/SDR; available to existing import-capable Admins

Grant imports:write with imports:read. New rows also require leads:create; matched updates require leads:edit.

Own new leads are assigned to the uploader; a different executor cannot change that planned assignment or bypass scope. Applies on the next server request after an Admin saves permissions.

Example: Grant shared history to a reviewer; grant write access only when they should execute imports.

Default: Off for Viewer/SDR; available to existing import-capable Admins

Grant imports:share with imports:read to list and view other uploaders’ jobs. Add imports:write to review/resume their jobs.

Incoming rows and matched leads outside the member’s current lead scope are redacted and cannot be updated. Shared access never implies lead access or promotes the member to Admin. Applies on the next server request after an Admin saves permissions.

Example: Grant shared history to a reviewer; grant write access only when they should execute imports.

Default: Admins have access; other members have none

Grant Hygiene read, run or AI summaries and Lead Assistant separately in People & access. Run/AI also require Hygiene read.

Every grant intersects current lead access, assigned-only workspace policy and active membership. Reports and chats remain creator-private; revocation prevents further reads and in-flight publication. No PAT access is added.

Default: No deletion; requires an explicit new preview and confirmation

Review current approximate total/archived lead counts, type DELETE ALL LEADS exactly and acknowledge permanent workspace-wide deletion. The preview is owner-bound and expires after ten minutes. Leads added before confirmation are included too.

After acceptance the operation cannot be cancelled. Lead changes and background processing pause for a five-minute in-flight grace period, then the existing scheduled worker removes records/files in resumable batches. Users, roles, permissions, configuration, personal preferences, standalone personal reminders, security audit and telemetry delivery evidence are retained. All old API idempotency receipts are redacted and expire, including standalone-operation retries. Removed imports must be uploaded anew. No in-app undo; provider backup/soft-delete retention is outside this control.

Example: Use this only to start a fresh pipeline. Export first if needed; a report is not a full file/history backup.

Default: Idle

Status refreshes while this section is open. Waiting, Running, Blocked and Completed are persisted. You may leave and return; cleanup continues independently of the browser.

Refresh status checks progress immediately. A failure retains the pause and cursor. After fixing service/storage access, an Admin can Retry cleanup with its current version. There is no automatic rollback or cancellation after partial deletion. Counts reflect acknowledged batch work; provider deletes retried after a crash may be undercounted. Imports and other lead-data writes pause with a cleanup-in-progress message and Retry-After guidance. Wait for Completed before retrying; the delay is not an estimated completion time.

Example: A network error does not mean cleanup was rejected. Refresh status or retry the same confirmation request; stable operation IDs prevent another reset.

Default: Current installed release

Explains why SalesDrone exists and shows the application version.

Refresh after a release to load current assets. This page does not change business data.