Page: Contact Us

Code: CONT Route: /contact Access: Public Priority: P1 Status: In Scope

Purpose

Provide a way for visitors to contact Peerloop for support, partnerships, press inquiries, and general questions. Reduce friction for potential users with questions.


Connections

Incoming (users arrive from)

Source Trigger Notes
HOME Footer 'Contact' link Primary entry
FAQP "Still have questions?" CTA Fallback from FAQ
ABOU "Get in Touch" link From about page

Outgoing (users navigate to)

Target Trigger Notes
FAQP "Check our FAQ first" link Reduce unnecessary contacts
HOME After form submission Return to home

Data Requirements

Entity Fields Used Purpose
contact_submissions name, email, subject, category, message, created_at Store contact form submissions

Sections

Hero

  • Headline: "Get in Touch"
  • Subheadline: "We're here to help. Reach out and we'll respond within 24 hours."

Contact Form

  • Name (required)
  • Email (required)
  • Category dropdown: General, Support, Partnership, Press, Creator Inquiry
  • Subject (required)
  • Message (required)
  • Submit button

Alternative Contact Methods

  • Email: support@peerloop.com
  • Social media links
  • Response time expectations

Quick Links

  • FAQ link
  • Help Center link (if exists)
  • Common question shortcuts

Office Info (Optional)

  • Company address
  • Map embed (if applicable)

User Stories Fulfilled

  • US-G020: Contact support with questions
  • US-G021: Reach out for partnership opportunities

States & Variations

State Description
Default Empty form ready for input
Submitting Loading state while form submits
Success Thank you message after submission
Error Error message if submission fails

Mobile Considerations

  • Form fields full-width
  • Category dropdown native on mobile
  • Submit button prominent and thumb-accessible

Error Handling

Error Display
Form submission fails Show error message with retry option
Invalid email format Inline validation error

Analytics Events

Event Trigger Data
page_view Page load source, referrer
form_start First field interaction field_name
form_submit Form submitted category, success

API Calls

Endpoint When Purpose
POST /api/contact Form submission Submit contact form and send email notification

Notes

  • Use Resend for email notifications to support team
  • Consider rate limiting to prevent spam
  • Store submissions in database for tracking