Contact Submissions

Contact Submissions

Purpose and when to use this record

BriskReview storesand respond to a storefront contact submissionsrequest aswhile partretaining ofits store, sender, subject, and original message.

At a glance

• Identify it by: Name, and Order Number.

• Check its business context: Store.

• Why care: Store, publication, consent, payment, and fulfillment states affect what customers see and what staff must act on; check the ecommercecorrect module.store Thisbefore generatedsaving.

  reference

Before you begin

You need the Brisk permission for the action you are taking on contact submissions. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

ViewReview recordContact Submission details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Contact Submission currently means. Verify Store, Name, Email, and sourcePhone locationbefore relying on it for thisa action.decision.

Confirm

Follow user-facingStore stepsto beforedetermine approvingwhether the issue is on this page.Contact Submission or on one of those linked records.

Next check: Use Store to interpret this Contact Submission. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Find and review recordscontact submissions

The evidence packet identifiesUse the viewContact Submissions list to find the correct record before opening or changing it. Compare Name, and sourceOrder locationNumber. Records with similar names or numbers can still belong to different Store.

• Keyword search checks Name, Email, Subject, Order Number, and Sent To.

• Narrow the list with Store filters.

• The date filter uses Created At; choose a range that matches the business event you are reconciling.

• The initial order emphasizes Created At. Select a column heading when you need a different comparison.

Open the Contact Submission whose Name, and Order Number match the task. If it is missing, clear the list filters and recheck Store, and Created At rather than creating a replacement immediately.

Fields and business rules

Brisk stores 9 user-relevant fields for this action.Contact ConfirmSubmission, user-facingincluding steps1 beforelinked-record approvingselection and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Field	Required	What it controls
Store	No	The store associated with this contact submission.
Name	Yes	Human-readable name for this contact submission.
Email	Yes	Email address recorded as email for this contact submission.
Phone	No	The phone recorded for this contact submission.
Subject	No	The subject recorded for this contact submission.
Message	Yes	The message recorded for this contact submission.
Source Ip	No	The source IP recorded for this contact submission.
Order Number	No	The order number recorded for this contact submission.
Sent To	No	The sent to recorded for this contact submission.

What happens next

Use Store to interpret this Contact Submission. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Common mistakes and troubleshooting

• The record will not save: Recheck Name, Email, and Message and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The values look right but the result is wrong: Open Store from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.