Solve CertCue setup issues without waiting on support.

1. Open Settings and download the vendor template.
2. Use Check headers on your existing CSV first if your spreadsheet uses different column names.
3. Paste one vendor per row with company, trade, contact, email, and owner; extra populated roster columns become vendor custom fields.
4. Re-upload a corrected roster when vendor details change; matching vendor names refresh the existing record instead of creating duplicates.
5. Keep starter requirements on during import so CertCue creates missing COI, license, W-9, and agreement rows where needed.
6. Review the confirmation before importing, then download the issue report if any rows need repair.

Your dashboard will show missing, expired, and expiring vendor paperwork instead of a flat spreadsheet, and repeat roster uploads refresh existing vendor details.

1. Open Settings and download the document template, or use a wide sheet with columns like COI Expiration or License Status.
2. Use Check headers before importing to confirm CertCue recognizes the vendor, status, date, and wide document columns.
3. Use any clear requirement name in the long-format Document type column, such as Safety certificate, Permit, or Vendor attestation.
4. Match rows to existing vendor names. CertCue updates an existing requirement when the same normalized name already exists.
5. Review the confirmation before importing and keep the issue report for any unmatched or invalid rows.

Repeat imports refresh the same named requirement rows instead of creating duplicates.

1. Open Dashboard and review the Import cleanup panel.
2. Download the cleanup report if another operator needs the full repair list.
3. Open each flagged vendor, edit vendor details, update document dates, or remove bad imported rows.

The workspace becomes trustworthy without a support request or full reset.

1. Open Settings and check the Safety snapshot panel.
2. Restore the latest safety snapshot if it was captured before the mistake.
3. Use full JSON backup restore when you need to replace the whole demo or cloud workspace with a saved backup.

The buyer can recover common mistakes without waiting for manual database help.

1. Open Settings and find Requirement templates.
2. Turn requirement types on or off for Licensed trade, Field service, and Standard vendor templates.
3. Apply templates or import vendors. Add Vendor recommendations and roster imports use the saved checklist.

New vendors start with the paperwork your team actually asks for.

1. Open Reminders to see the open follow-up queue.
2. Copy a request, open an email draft, export follow-ups for mail merge, or download the calendar file.
3. Open a vendor detail page when one vendor needs a packet with every open requirement grouped together.

Operators can act from CertCue instead of manually recreating the queue in email or a calendar.

1. Open Settings and find Automatic reminder delivery.
2. Add the reply-to email your vendors should answer, then choose weekly or daily delivery.
3. Download the reminder preview to review each open follow-up, send-ready row, skipped row, and missing contact email before enabling delivery.
4. Make sure each vendor in the queue has a contact email; missing emails still need copy-request handling.
5. Save the setting. The scheduled sender skips duplicate document/contact sends on the same day.

Reminder delivery can run from the server without rebuilding emails or asking support to send them.

1. Open the vendor detail page and review the Vendor packet requirements.
2. Click Copy upload link to create a secure link for the open missing, expired, or expiring requirements.
3. Send that link to the vendor. If upload links are not configured yet, use Copy packet or Email packet as the fallback.
4. Open Settings > Vendor upload links to review recent links, see whether a vendor viewed or submitted, and revoke an open link that should stop working.
5. After submission, the requirement stores the file reference and moves to current for buyer review.

Vendors can upload paperwork, and buyers can review or revoke upload requests without asking support to update records.

1. Open Settings and find Team access.
2. Enter the teammate's invited work email, optional name, and access level.
3. Create the invite link, then copy the generated message and send it only to that teammate.
4. The teammate opens the link, signs in with the invited email, and joins the existing cloud workspace.
5. Use the recent invites list to refresh status or revoke a pending link that was sent to the wrong person.
6. Use Active team members to change Admin/Member access, transfer ownership from the current owner, or remove a teammate who should no longer use the workspace.

A buyer can add, review, transfer, and remove operators without asking support to provision accounts or move data between workspaces.

1. Open Settings and find Support packet.
2. Copy or download the packet. It includes storage mode, service readiness, setup health, cleanup issues, open follow-ups, and recent activity.
3. Attach or paste the packet into the approved support path after removing anything you do not want to send.
4. Do not include passwords, card details, or private insurance policy contents.

Support gets useful context in one message instead of asking the buyer to recreate the workspace state by hand.

1. Open Settings and find Buyer trust packet.
2. Copy or download the packet. It includes product boundaries, workspace data types, storage mode, export/delete controls, billing boundaries, and service readiness.
3. Share it for internal review or marketplace prep before sending private vendor documents.
4. Review Privacy and Terms before moving production data into a signed-in cloud workspace.

Buyers get a clear trust and data-handling answer without a custom support exchange.

1. Open Settings and export vendor CSV, document CSV, audit-log CSV, workspace report, or a full JSON backup before changing data.
2. Use Clear workspace data when an owner/admin needs to remove vendors, documents, reminders, settings, and activity from the current workspace.
3. Restore the latest safety snapshot or a JSON backup if the clear or import was a mistake.
4. Send a data request through the approved support path only for account-level questions, legal/privacy requests, or anything that cannot be completed from Settings.
5. Include the workspace email, company name, and a support packet; do not include passwords, card details, or private policy contents.

Buyers can export, restart, or request data help with a clear path instead of waiting for manual database work.

1. Copy the support report ID from the error screen if one appears.
2. Create a support packet from Settings if the app still opens.
3. Send the report ID, support packet, workspace email, company name, and what you were trying to do.

Support has the exact context needed without asking the buyer to repeat the same troubleshooting steps.