Taboo CRM
Modern CRM operations for customers, workflows, and payments.
Welcome back
Taboo CRM
Account Access
Taboo CRM
Secure Link
Taboo CRM
Signed in as
Search results will appear on the left.
My Profile
The Home page combines work assigned to you with operational information from across the CRM. What you see can vary by your active role, merchant assignments, and the selected followup scope.
Use the calendar and work lists first, then review alerts and pipeline counts. The performance containers provide context and do not require daily action.
Shows the total number of current merchant records that have not been soft-deleted.
Data shown: Merchants enter this count when they are created or imported. A merchant leaves the count only when it is soft-deleted.
Shows active merchant and user followups whose scheduled time has passed.
Data shown: Followups are created from merchant and user records. The total follows the My Followups or All Followups scope selected below.
Shows active merchant and user followups scheduled from now through the next 14 days.
Data shown: The total is calculated from saved followup dates and follows the selected followup scope.
Shows the number of auditable CRM events recorded during the last 14 days.
Data shown: The application creates audit events automatically when tracked actions occur, such as merchant changes, workflow actions, and administrative updates.
Displays up to 25 active merchant and user followups that are overdue or due within 14 days. Overdue items are shown first.
How to use it: Admin users can switch between My Followups and All Followups. Use the month arrows and calendar days to view a specific date. Select Show upcoming to return to the rolling work list. Open a row to view its merchant or user, or use Reschedule and Complete directly from Home.
Data shown: Followups are created and assigned on merchant and user records. Calendar markings combine the merchant and user followups visible under the selected scope.
Lists appointments for the date selected on the Home calendar. The default date is today.
How to use it: Select an appointment to open the merchant. Create or change appointments from the merchant's Appointments tab.
Data shown: Appointments are created on merchant records and appear when you are assigned to the appointment as an agent, manager, ISO, processor, or owner. All Followups allows Admin users to view the broader schedule.
Displays active company messages intended for your current role.
Data shown: Administrators create announcements under Admin > Operations > News & Announcements and control their audience and active dates.
Shows the eight merchants with the most recent local activity.
How to use it: Select a row to open the merchant Overview.
Data shown: A merchant appears after a local save or an auditable merchant action. The date reflects the newest of those recorded activities, not the original import date.
Lists merchants whose banner alert is currently enabled, with the merchant name, status, and alert date.
How to use it: Select an alert to open the merchant Overview and review or change the alert.
Data shown: Alerts are created when an authorized operator enables Alert On in the merchant Overview.
Compares your pipeline with the Total-Apps pipeline for Lead, Pre-app, Incomplete, Pending, Processing, and Integrating merchants.
How to use it: Select any nonzero count to open Merchant Search filtered to that status.
Data shown: My Pipeline counts merchants assigned to you as manager. Total-Apps Pipeline counts all current merchants in each displayed status. On Hold work due today is included with your Pre-app workload.
Shows your Accounts Received, Submitted, Approved, and Closed totals for the previous calendar month.
Data shown: Totals are calculated from recorded merchant status changes and merchants assigned to your user account. Missing activity is displayed as zero.
Shows team account activity for the three previous calendar months.
Data shown: Received, Submitted, Approved, Closed, and Processing totals are calculated from merchant status history. A dash means that a metric is not currently populated.
Shows how many current merchants are assigned to you under each assignment type.
Data shown: Counts come from the Manager, Processor, Agent, ISO, Referral, and Biz Dev assignments saved on merchant records. Only assignment types with merchants are listed.
These charts are reference-only views of data already summarized elsewhere on Home. They do not change records.
Visualizes your Received, Submitted, Approved, and Closed counts for the previous month.
Data shown: Uses the same status-history totals as the personal performance container.
Compares team Received, Submitted, Approved, and Closed totals across the previous three months.
Data shown: Each colored series is calculated from recorded merchant status transitions.
Compares how many distinct accounts entered Processing in each of the previous three completed months.
Data shown: Counts come from recorded merchant status transitions, not the current active portfolio.
Shows the relative size of the current Total-Apps pipeline by application status.
Data shown: Uses the same current merchant counts displayed in the Total-Apps Pipeline column.
The Merchants workspace contains the business profile, application workflow, pricing, operational setup, compliance information, and history for each merchant. The merchants and tabs you can see depend on your active role, assignments, and merchant-tab permissions.
Search for a merchant first, select the result, and then use the detail tabs. Save buttons apply only to their named section, and the application warns when another operator has saved newer information.
Finds merchants by business name, MID, CID, contact, phone, email, or website and can be narrowed to a merchant status.
How to use it: Enter any known information, optionally select a status, and select Search. Results remain hidden until a search is performed.
Data shown: Search reads current merchant profiles within your active role and assignment scope.
Provides additional filters for assignments, business and opportunity categories, account information, and related merchant attributes, plus a selectable sort field and direction.
How to use it: Expand More filters, choose only the criteria you need, and run the search again. Admins can include soft-deleted merchants for review or restoration.
Data shown: Filter choices come from current CRM catalogs and active assignment users.
Each result identifies the merchant by name and MID and includes its current status and useful contact or assignment context.
How to use it: Select a result to open the first merchant tab you are permitted to read. Use Previous and Next to move through large result sets.
Data shown: Results use saved merchant profile, status, and assignment data and exclude records outside your access scope.
Exports all merchants matching the current search, filters, sort, and access scope in CSV or Excel format.
How to use it: Run the desired search, select Download, and choose CSV or XLSX. The export is not limited to the visible page.
Data shown: The file is generated from the same current-database query used by Merchant Search.
Creates a complete initial merchant profile with required business, contact, status, risk, and assignment information.
How to use it: Admin users select New Merchant, complete every field marked with a red asterisk, and submit. The new MID is assigned automatically and the record opens after creation.
Data shown: Catalog choices and eligible assignment users come from the current CRM. Creation also initializes the merchant's starting workflow history.
The header shows the merchant name, MID, status, and alert state. Copy Link creates a relative link to the current record.
How to use it: Admins can duplicate a merchant's business profile and assignments, soft-delete a record with a reason, or restore a deleted merchant. Deleted merchants are read-only until restored.
Data shown: Status and alert come from Overview. Lifecycle operations are audited; duplication intentionally excludes sensitive values and child history.
Maintains the legal and DBA profile, contact details, addresses, identifiers, account settings, status, risk level, categories, processing selections, assignments, alert, and contract dates.
How to use it: Save profile changes with Save Overview and assignments with Save Assignments. Address buttons standardize legal or DBA addresses; copying the legal address can also preserve its validation status. Approve Contract records today's approval and a three-year expiration.
Data shown: Values come from the merchant profile and current catalogs. Required fields, formats, and catalog selections are validated by both the form and API.
Adds merchant notes with selectable Manager, Agent, ISO, Processor, and Referral visibility. Older notes and activity remain available through separate 25-item pagers.
How to use it: Enter a note, select its intended audience, and save. Authorized users can delete eligible notes. Activity History is a read-only timeline of notes, status changes, and audited merchant events.
Data shown: Visibility and merchant access determine which notes appear. Activity entries are created automatically by tracked workflows.
Schedules merchant work from a calendar with 15-minute time slots and separates Upcoming Appointments from Appointment History.
How to use it: Select New Appointment, choose a date and contiguous time blocks, assign the applicable users, add the action and note, and save. Upcoming appointments can be edited or cancelled.
Data shown: Existing appointments populate their time slots. The scheduler rejects overlapping appointments for the assigned user and feeds eligible Home calendars.
Runs merchant workflow commands such as sending applications, requesting documents, processor pre-approval, return for signature, processor submission, lifecycle emails, templates, and referrals.
How to use it: Choose an action, review its recipients and generated content, attach files when supported, and submit. Actions validate required status, recipient, or application information before making changes.
Data shown: Forms use the merchant's contact and assignment context plus database-managed templates. Email is queued in the Email Outbox, while status, notes, and history are updated transactionally.
Stores private merchant attachments by category and separately lists completed signed applications.
How to use it: Uncategorized is the default; choose a more specific category when appropriate, select a file, and upload. Authorized users can download or delete available files.
Data shown: Files must meet the displayed size and type limits and pass a security scan before private storage. Signed applications are created by the public signature workflow.
Maintains additional merchant contacts separately from the primary contact on Overview.
How to use it: Enter a name, title, email, and phone to add a contact. Existing contacts can be revised or deleted individually.
Data shown: Contacts are independent child records saved to the selected merchant and validated using the shared contact rules.
Maintains card pricing, interchange and check pricing, monthly and service fees, risk and authorization fees, gateway and PCI fees, and other fees.
How to use it: Review the merchant-specific values, enter percentages or currency in the matching fields, and save. Blank numeric values display as zero.
Data shown: Values come from the merchant's current rate record or selected rate template. Field-specific limits prevent invalid percentages and amounts.
Records sales volume and ticket information, recurring billing, transaction-channel percentages, and electronic versus manual completion percentages.
How to use it: Enter sales amounts and percentage mixes, review each calculated total, and select Save Transactions.
Data shown: Values come from the merchant transaction profile. Missing percentages display as 0.00, and current saves are protected from stale edits.
Maintains settlement banking, account ownership and type, owners or officers, and optional trade-reference contacts.
How to use it: Use the eye buttons only when sensitive values must be reviewed. Add or remove owner rows as needed, expand Trade Reference when applicable, and save the section as one update.
Data shown: Sensitive identifiers and account values are masked by default. Reveal access, removals, and saves are audited.
Configures deployment profile, programming and services, shipping, billing, terminals, printers, check readers, supplies, and related setup notes.
How to use it: Apply a deployment profile to populate recommended choices, then adjust the merchant-specific controls. Printers and check readers are collapsed until needed.
Data shown: Profiles come from Admin merchant setup. Applying a profile changes the unsaved form; Save Deployment creates or updates this merchant's deployment record.
Captures merchant history, seasonal and sales profile, card acceptance, telephone-order activity, refund policy, site survey, premises, business hours, timezone, and employee information.
How to use it: Complete the sections that apply, choose seasonal months and advertising methods, and save. Percentage fields accept values from 0 through 100.
Data shown: Values are the merchant's application and site-survey details, including normalized imported seasonal-month information.
Tracks reported compromise, PCI-DSS status, scan and questionnaire dates, SAQ validation type, and the current compliance document.
How to use it: Select the applicable SAQ type, use its guidance when needed, update the compliance review, and upload or replace the document separately.
Data shown: SAQ choices and descriptions come from Admin configuration. Compliance files use the same private, security-scanned storage controls as merchant documents.
Shows commission profiles for the assigned Agent, ISO, Referral, and Biz Dev parties and maintains the merchant's commission splits.
How to use it: Review the risk-tier profile rates, enter the applicable splits, and confirm the displayed total before saving.
Data shown: Assigned-party profile rates come from user commission configuration; saved merchant splits feed commission calculations and reports.
Maintains underwriting checklist and risk-review information, provides a normalized shared-contact-phone check, and records checklist approval as PASS or FAILED.
How to use it: Complete and save the checklist, check the contact phone for related merchants, then use Checklist Approval when the review is ready for a recorded decision.
Data shown: Shared-phone results include accessible matching merchants and status context. Approval records the reviewer, result, note, and applicable workflow history.
Shows the merchant's processor history and associated processing identifiers and dates.
Data shown: Entries are created from imported processor history and current processor workflow records. This tab is a reference view and does not edit those records.
The Users page is the administrative workspace for finding user accounts, creating users, managing access, and maintaining user-related records. Only Admin users can open the Users page or another user's record.
Every signed-in user can open their own profile and password-reset form by selecting the avatar circle in the upper-right corner. This self-service profile does not provide access to the Users workspace.
Finds users by name, username, email, or company. Role and status filters can narrow the results to Active, Pending Approval, Inactive, or all users.
How to use it: Enter any known information, choose optional filters, and select Search. Results remain hidden until a search is performed.
Data shown: Search reads current user profiles, assigned roles, and account status from the CRM database.
Each result shows the user's name, status, email or username, User ID, and assigned roles.
How to use it: Select a result to open the user record. Use Previous and Next to move through large result sets.
Data shown: Status reflects whether the account is active, awaiting approval, or disabled. Disabled users cannot sign in.
Exports the users matching the current search and filters in CSV or Excel format.
How to use it: Run a search, select Download, and choose CSV or XLSX.
Data shown: The export uses the same query and filters as the visible search results, without limiting the file to the current page.
Creates a user with a required name, unique login username, email, phone, and at least one role. Company and active status can also be set.
How to use it: Leave Send password setup email selected to queue a single-use setup link. Clear it only when an initial password of at least 10 characters will be entered directly.
Data shown: A new record receives its User ID from the database. The username is the value used at login.
Shows the selected user's name, username, email, phone, company, roles, User ID, and account status.
Data shown: Values come from the saved user profile and role assignments. Profile changes are made in the administrative sections below.
Updates email, phone, company, and whether the account is active.
How to use it: Clear Active to disable an account and prevent future logins. Select Save User after making changes.
Data shown: The status badge at the top of the record updates from the saved account status.
Controls which roles the user can select during sign-in and which role-based permissions apply.
How to use it: Select all roles the user is authorized to perform, then save the assignments. Detailed report and merchant-tab access may also be controlled by administrative permission settings.
Data shown: Available roles come from the current role catalog; checked roles are the user's saved assignments.
Maintains applicable Manager, ISO, Processor, or Referral reporting relationships and lists merchants and users connected to the selected account.
How to use it: Save parent relationships when they apply. Select linked merchant names, MIDs, or usernames to open the related record; use the pagers for longer lists.
Data shown: Relationship choices come from active users with the required role. Lists are built from saved user relationships and merchant assignments.
Lets an Admin review the application as the selected active user and role without granting write access during the preview.
How to use it: Choose an assigned role and begin the temporary session. Exit the preview to return to normal Admin access.
Data shown: The preview uses the selected user's assignments and permissions. Starting and ending the session are audited.
Appears for accounts awaiting administrative approval.
How to use it: Review the profile and roles, then approve the user to activate the account and queue a password setup email.
Data shown: This section appears only while the account has Pending Approval status.
Admin Password Reset sets a new password directly. Password Setup Email queues a single-use link so the user can choose a password privately.
How to use it: Prefer the setup email when the user can receive email. Use direct reset only when operationally necessary; passwords must meet the displayed minimum length.
Data shown: Password change and setup-email events are recorded in administrative history without storing the password in the audit detail.
Appears for users assigned the Referral role and manages their private referral-agreement link and agreement history.
How to use it: Send a new expiring agreement when needed. A new request invalidates an earlier pending request.
Data shown: History shows saved sends, expiration, and completion information for the selected referral user.
Adds and maintains individual or department contacts associated with the user, including title, email, work phone, cell phone, fax, and notes.
Data shown: Contacts are separate child records created and updated from this tab. Deletes require confirmation.
Adds and maintains labeled addresses with company, website, street, city, state, postal code, country, phone, and fax details.
Data shown: Addresses are separate child records saved to the selected user and protected against overwriting a newer edit.
Maintains the user's bank name, business or personal account type, ABA routing number, and account number.
How to use it: Sensitive values are masked by default. Use the eye button only when the full value must be reviewed or replaced.
Data shown: Banking values come from the selected user's saved banking profile. Sensitive-value access and changes are auditable.
Uploads, downloads, and deletes private documents associated with the user.
How to use it: Enter a document name, choose a category and file, then upload. Files must meet the displayed size and type rules and pass a security scan before storage.
Data shown: The list shows stored document metadata, uploader, date, file size, and whether the underlying file is available.
Adds, edits, and deletes administrative notes about the selected user. Notes are shown 25 per page with the author and timestamp.
Data shown: Notes are created by authorized operators on this tab and retained in the user's history according to application audit rules.
Creates dated work reminders, assigns them to an eligible user, and supports saving, completing, or reopening existing followups.
How to use it: Choose the responsible user, date and time, and note. Open followups can appear in the assigned user's Home calendar and work list.
Data shown: Followups are saved against this user record and listed 25 per page, including their current completion state.
Provides a paginated timeline of recorded activity associated with the user, including the event title, time, actor, and available detail.
Data shown: Entries are created automatically by audited user operations and imported user history. This tab does not change records.
Every signed-in user can select the avatar circle in the upper-right corner to review their own name, username, email, phone, company, roles, User ID, and status.
How to use it: This is the correct path for non-Admin users to view their own profile because the top-level Users menu is intentionally hidden from them.
Data shown: The modal loads only the currently authenticated user's profile.
Allows a signed-in user to change their own password by supplying the current password and confirming a new password.
How to use it: Open the avatar profile, enter the current password, then enter and confirm the new password.
Data shown: A successful change updates the current account and records a password-change audit event without exposing the password.
The Support workspace is used to request planned work, report product defects, review merchant-status guidance, and standardize an address. Ticket visibility follows the signed-in user: regular users see their own tickets, while Admin users can review all tickets.
Use a Support Ticket for a request that needs prioritization, review, comments, files, or delivery tracking. Use Submit Bug when existing behavior appears to be incorrect and should be investigated as a defect.
Finds tickets by ticket number, title, or description. Status, priority, and request type can be used to narrow the list.
How to use it: Enter any known information, choose optional filters, and select Search. Use Previous and Next to move through results, which are shown 25 per page.
Data shown: Regular users see tickets they requested. Admin users see all current tickets. Deleted tickets are excluded.
Shows the ticket number, title, request type, priority, status, requester, and most recent update time.
How to use it: Select View to open the full ticket. Tickets with recent comments, documents, or administrative changes move toward the top of the list.
Data shown: Priority and status come from the saved ticket. Updated reflects the newest recorded ticket activity.
Creates a trackable request with a title, request type, requested ETA date, priority, and description. Attachments are optional.
How to use it: Select New Ticket, complete every required field, add any supporting files, and submit. The ETA cannot be earlier than today.
Data shown: Request types are maintained in the CRM. A new ticket begins in Submitted status and records the signed-in user as its requester.
The open ticket shows its requester, type, priority, status, ETA, last update, and full original description.
Data shown: The summary combines the original request with the latest saved administrative review values.
Provides a dated conversation between the requester and administrators without changing the original description.
How to use it: Enter a new comment and select Add Comment. Reload protection prevents a comment from being applied over a newer ticket revision.
Data shown: Existing comments show the author and time they were added. Comment activity is also recorded in ticket history.
Adds supporting PDF, Word, or image files to a ticket and allows authorized users to download them privately.
How to use it: Choose a file and select Upload Document. Every file must meet the displayed upload limits and pass a security scan before storage.
Data shown: The list shows the stored filename, upload time, and uploader. Only Admin users can delete ticket documents.
Allows an Admin to move a ticket through Submitted, Approved, Declined, In Development, and Completed; revise the ETA; record estimated time and delivery date; and add a review note.
How to use it: Review the request and discussion, update the applicable fields, and select Save Review. Delete Ticket is reserved for removing an unusable or duplicate ticket.
Data shown: This section appears only for Admin users. Saves are revision-protected and create a ticket event and administrative audit record.
Shows the chronological event ledger for the ticket, including event type, status, user, note, and timestamp.
Data shown: History entries are created automatically when the ticket is submitted, reviewed, commented on, or receives document activity.
Reports behavior that appears incorrect. A report can include severity, the page or area, a description, reproduction steps, and expected and actual results.
How to use it: Enter a concise title and enough detail to reproduce the problem. Page / Area is entered manually. Add supporting files as needed, or paste a screen snip into Description. Select Submit Bug and wait for the confirmation message.
Data shown: The CRM records the signed-in user, submitted details, browser name, and browser user-agent information. Admins review reports under Admin > Configuration > Bug Reports.
Provides a reference table explaining how each merchant status should be used.
Data shown: Status names, order, and descriptions come from the current CRM database. Merchant status configuration determines which definitions are available.
Checks a manually entered street address with the address-verification provider selected by an administrator.
How to use it: Enter the street, optional secondary address, city, two-letter state, and ZIP Code, then select Validate Address. Review the standardized result and any provider message.
Data shown: The standardized address is returned by the configured provider. This standalone tool does not save the address to a merchant or user record. If verification is disabled, the tool displays that status instead.
| Sr. No. | Status Title | Status Description |
|---|---|---|
| Loading status descriptions... | ||
Uploads are scanned and staged for review. No processing or commission data changes until an error-free batch is applied.
CID-based Agent, ISO, Referral, and Total-Apps splits are validated and staged as one atomic batch.
Canonical login usernames are matched to active users with the corresponding role. Any invalid row rejects the entire batch.
These source notes reference UIDs that no longer exist. Map each note to a verified user or discard it with a documented reason.
These source banking profiles reference UIDs that no longer exist. Sensitive values remain masked. Map only to a verified user without an existing banking profile, or discard the record with a documented reason.
These records either reference a UID that no longer exists or a source file that was not present in the copied archive. Recoverable orphan files are scanned, hashed, and copied into private storage only after they are mapped to a verified user.
Search results will appear on the left.
Create the merchant with its required profile and assignments.