Skip to main content

Contact Forms

Contact forms let you capture information from visitors on your publicly published documents. When enabled, a contact button appears on the public document page, opening a form that submits responses directly into a Copera project board. This turns your public-facing documentation into a lead generation or inquiry capture tool.

How It Works

The contact form feature connects a public document to a project board in your workspace. When a visitor fills in the form, their submission is created as a new row in the specified board table. Your team can then manage, track, and respond to submissions using all the board features --- status fields, assignments, automations, and more.

Setting Up a Contact Form

To add a contact form to a public document:

  1. Publish the document --- The document must be published publicly first. Open the Share dialog, go to the Public tab, and click Publish. See Sharing & Permissions for details.

  2. Enable the contact form --- In the public sharing options, toggle Contact Form on.

  3. Select a board and table --- Choose the project board and table where form submissions should be stored. The board must already exist in your workspace. You can also select a specific view if needed.

  4. Customize the button label --- Optionally change the text on the contact button that appears on the public page (for example, "Contact Us", "Get in Touch", "Request a Demo").

  5. Save --- Click Save to apply the settings. The contact form is now live on your public document.

What Visitors See

When a visitor views your public document, they see a contact button (typically in the corner or footer of the page). Clicking the button opens a form dialog where they can enter information.

The form fields are determined by the board table's form view. This means you have full control over what information you collect --- name, email, phone number, company, message, or any custom fields you have defined on the board.

Managing Submissions

Submissions arrive as new rows in your project board. You can:

  • View submissions in any board view --- List, Kanban, Calendar, or any other view configured on the table.
  • Assign team members --- Use people fields to assign submissions to the appropriate person for follow-up.
  • Track status --- Use status fields to move submissions through your pipeline (New, In Progress, Responded, Closed).
  • Automate responses --- Set up board automations to notify your team when a new submission arrives or to move submissions through predefined workflows.
  • Filter and sort --- Use board filters to segment submissions by date, status, or any other field.

Use Cases

ScenarioHow to Set It Up
Lead capturePublish a product overview document with a "Request a Demo" contact form linked to a Sales Leads board.
Support inquiriesPublish a help article with a "Contact Support" form linked to a Support Tickets board.
Event registrationPublish an event information page with a "Register" form linked to an Event Attendees board.
Feedback collectionPublish an internal process document with a "Give Feedback" form linked to a Feedback board.

Best Practices

  • Keep forms short --- Ask for only the information you need. Long forms discourage completion.
  • Use clear labels --- Make sure board fields have descriptive names, since they appear as form field labels.
  • Set up notifications --- Configure board automations to alert your team immediately when a new submission arrives.
  • Review regularly --- Check your submissions board frequently so inquiries do not go unanswered.

Next Steps