How to add a contact form to your link-in-bio page

A link-in-bio page is often the first place a visitor sees an offer and a way to respond. A contact form is useful when the owner needs a reply address and a short explanation before answering: a photographer checking availability, a small studio discussing a project, or a shop handling a specific product question. A direct email or WhatsApp link is better when the task is a quick conversation in that channel. Neither path is automatically better; choose the one you can actually monitor and answer.

Write the visitor's task in plain language before adding a block. Tell us about your project is clearer than Contact us if you need project inquiries. Ask about a custom order is clearer than Send a message when the page shows commissioned goods. Do not call a form a booking system if it only collects a request. The visitor should understand what happens after sending it and whether someone will reply.

A form floating at the bottom of a long link list asks the visitor to remember why they came. Put a concise statement of what you offer above it and a small amount of proof nearby: selected work, service scope, opening area, or a current example. Then make the form title match that promise. If the owner sells several unrelated services, use the description to tell the visitor what to include in the message rather than asking them to guess.

Keep the request proportional. The current Linkrise public Contact form asks for name, email, and message, followed by required consent with a link to the privacy policy. The Studio authoring screen lets the owner set a title, description, and success message; it is not a general custom-field builder. Do not promise a phone field, file attachment, mailing-list opt-in, automatic CRM sync, or bespoke survey questions that the current block does not offer.

Open the Linkrise profile you intend to share and go to the Links editor. Add a Contact block, then give it a title that describes the purpose of the inquiry. The optional description can ask for only the context you need to respond, such as the kind of project and a preferred timeframe. Write a short success message that confirms receipt without promising a response time you cannot maintain. A message such as Thanks, we received your note is safer than We will reply within an hour unless that service level is real.

Save the block and publish the page. The block follows the profile's visual theme, so it should look like part of the page, but the owner still needs to inspect the mobile public view. If a block is hidden, unpublished, outside its configured visibility period, or the account cannot serve the public page, visitors cannot use it. Do not treat the editor preview as proof of delivery. Open the signed-out public URL after every meaningful change.

The public form requires the visitor to consent before Linkrise stores and shares the submission with the profile owner. It links to the privacy policy. This is a collection boundary, not permission to ask for anything. A first inquiry usually needs enough detail to route a reply, not a passport number, health history, payment card, or other sensitive record. If a later process requires sensitive information, use a system built and disclosed for that purpose.

Make the visible labels and instructions easy to understand on a phone. The W3C recommends labels that identify each control and clear feedback after a form action. Linkrise provides the basic fields and a success or error state, but the owner controls the surrounding promise and follow-up. The success message should say the request was received. It should not imply that a booking, contract, payment, or human review has already happened.

Open the public profile in a signed-out browser and send one test message with an email address you control. Check that the form is visible, the privacy link opens, consent is required, and the button shows a clear result. Test an empty required field and a malformed email before sending the valid test. On a narrow phone viewport, confirm that the keyboard does not hide the submit action and that errors can be read without hunting around the page.

A success message on one device is only the first half of the test. Return to the owner account and export submissions for that Contact block from the Links editor. Check that the new row contains the expected email, message, block title, and timestamp. Do not send a customer's real data just to test. If the export is empty, do not assume delivery because a green preview looked right; investigate the public URL, the block's saved state, and the response before distributing the page.

Linkrise stores valid submissions and provides an owner-scoped CSV export from the saved Contact block. The current product does not promise an automatic email notification, team inbox, CRM sync, or automatic reply. Someone must decide when to export, who is allowed to open the CSV, how quickly to respond, and where the actual outcome is recorded. A form with no owner is only a new place for messages to go unanswered.

Treat the CSV as personal data. Keep access limited, avoid forwarding it casually, and remove local copies when no longer needed under your own policy. Linkrise applies bounded retention to stored submissions and does not persist the visitor's raw IP with the inquiry. Rate limits and anti-abuse checks can temporarily reject a submission; if missing an inquiry would be serious for your business, offer a secondary contact path that you can monitor.

Imagine a fictional independent design studio whose page shows two recent projects and one service link. Its Contact title is Ask about a project. The description asks for the type of work, desired start month, and a short outline in the message field. The success text says the request has been received. It does not quote a price or promise acceptance. A visitor can see the work, understand the request, and send a message without first opening a separate mail app.

The studio tests the page while signed out, downloads the CSV from the block, and confirms the test row. It then records real follow-up in its own workflow. If it later wants detailed briefs, contracts, files, scheduling, or deposits, it sends qualified inquiries to the specialist system that handles those steps. The public Linkrise form remains a first-contact path rather than pretending to be the entire client process.

Profile visits and contact-intent activity can show that people reached or chose a contact path, but they are not the same as accepted submissions. The exported Contact rows are the evidence that the form received an inquiry. Neither metric proves a reply was sent, a booking was accepted, or revenue was collected. Confirm each downstream step in the email, scheduling, invoicing, or customer system where it actually occurs.

Review the page using comparable periods and a small set of questions. Did the visitor understand why to contact you? Was the form close to relevant proof? Did valid submissions arrive, and were they answered? If not, fix the title, description, or location before adding more fields or claiming a conversion lift. The useful result is a clear request and a responsible response, not a larger number in a dashboard.