Arc
ComponentsBlocksDocsPricingTry the demo
Introduction
Installation
Theming
Motion
AI and MCP
Changelog
Metrics dashboard
KPI drilldownNew
Metric explorer
Revenue explorer
MRR waterfall
Cohort retention
Usage forecast
Journey flow
Connected scatterNew
Market terminalNew
Budget varianceNew
Small multiplesNew
Line replayNew
AI chatNew
AI composer
Agent runNew
SidebarPro4
Page header
Command palette
Notification center
Empty states
Login and sign up5
OTP input
Multi-step formPro
Settings page
Security settings
Billing overview
Usage billingNew
Team members
Invite peopleNew
Team directory
Roles and permissions
API keys
Webhooks
Integrations
Plan comparison
Pricing calculatorNewPro
Usage pricingPro
Cart drawerNewPro
Checkout summaryNewPro
Invoice studio
Wallet card
Product listingNew
Product detailNew
Inbox triage
Support conversation
Support widget
File upload
Media playerPro
Week calendarNew
Availability picker
Project board
Release readiness
Hero sectionNew
Hero signupNewPro
Scroll storyNewPro
Spotlight gridNewPro
Feature bentoNewPro
Comparison tableNew
Logo marquee
Studio perspectivesPro
Stats bandNew
Changelog feed
FAQ sectionNew
Contact sectionNew
Team showcasePro
Blog gridNew
Site headerNew
Site footerNew
CTA sectionNew
Newsletter signupNew
Revenue globe
Customer galaxy
Semantic zoom
Layout morph
What’s new80 new
BlocksContact section

Contact section

A validated contact form that morphs into a confirmation, support channels, and office cards with local times.

$pnpm dlx shadcn@latest add @uiarc/contact-section
Live block · sample data

When to use

  • Contact pages and sections on marketing sites.
  • Sales or support pages that list several channels with response times.
  • Companies with offices in several time zones.

When not to use

  • Use support-widget for an in-app help launcher.
  • Use signup-form or login blocks for account flows.

Installation

Add Contact section with the shadcn CLI, or copy the source by hand.

$pnpm dlx shadcn@latest add @uiarc/contact-sectionpnpm dlx shadcn@latest add @uiarc/contact-section

Adds the block and its local dependencies, and installs motion, lucide-react. First time? Add the @uiarc registry to components.json, or use the full URL:

Usage

Use this as a starting point and replace the sample data with your own.

example.tsx
1import { ContactSection } from "@/registry/blocks/contact-section/contact-section";2 3export function Contact() {4  return (5    <ContactSection6      title="Talk to us"7      topics={["Sales", "Support"]}8      onSubmit={async message => {9        const response = await fetch("/api/contact", { method: "POST", body: JSON.stringify(message) });10        if (!response.ok) throw new Error("Could not send");11      }}12    />13  );14}
Built fromMotion

API reference

2 parts. The first is the root.

ContactSection

A contact section in three layouts: a validated form that springs into a confirmation, a list of channels with detail, or offices with live local times and open status.

PropTypeDefaultDescription
variant"form" | "channels" | "offices""form"Layout.
titlestring–Section heading.
descriptionstring–One line under the heading.
topicsstring[]["Sales", "Support", "Partnerships", "Press"]Topics offered in the form as a radio group of chips.
onSubmit(message: { name; email; topic; message }) => void | Promise<void>–Called with a valid message. Reject to keep the form and show an error; resolve to show the confirmation.
channels{ value; label; meta; icon?; detail: ReactNode }[]contactExampleChannelsWays to reach you for the channels variant.
channelstring–Selected channel (controlled).
defaultChannelstring–Initial channel when uncontrolled.
onChannelChange(value: string) => void–Called when the channel changes.
offices{ city; timeZone; address: string[]; email?; hours?: [number, number] }[]contactExampleOfficesOffices. timeZone is an IANA zone; hours default to 9 to 18 local time.
classNamestring–Extra class on the section.

ContactSectionBlock

Default export: a preview with a layout switcher. Messages are simulated and never sent.

PropTypeDefaultDescription
variantContactSectionVariant"form"Initial variant.

Keyboard interactions

Arrow keys
Move between topic chips, which form a radio group.

Accessibility

  • Fields use labelled Arc Input and Textarea; errors appear after the first submit and update as you type.
  • A failed send shows a role="alert" message and keeps the form.
  • Office open status is written out, not shown by color alone.

Motion

  • The form card springs into the confirmation; faces slide along one axis in the direction of travel out of a soft blur.
  • The topic highlight glides between chips.
  • Reduced motion swaps faces without travel.

Responsive behavior

  • Container queries: below 820px the form layout stacks and the channel list becomes a horizontal scrolling row; below 520px field rows stack and the submit button fills the width.

Performance

  • The offices variant re-renders every 15 seconds to keep local times live; other variants have no timers.

Notes for AI

Give your coding assistant the Markdown reference instead of screenshots.

  • Without onSubmit the form only simulates sending; always wire it in production.
  • Offices compute local time and open status with Intl.DateTimeFormat in each timeZone.
  • Composes Arc Input, Textarea, Button, CopyButton, SegmentedControl, and Avatar.
/components/blocks/contact-section/markdown

The full library index for assistants is at /llms.txt.

Related

Login and sign up: Sign upBlockAn account creation flow with field validation, password strength, and a clear completion state.Support widgetProBlockAn in-app help launcher that grows into live article search, reading, and a chat with your team.FAQ sectionBlockFAQs as an accordion, a topic rail, or a searchable list that highlights matches.Site footerBlockA website footer with link columns and newsletter, a minimal layout, and a large fading Arc mark.
PreviousFAQ sectionNextUsage billing
Arc · 75 block pagesllms.txt

On this page

  • Preview
  • When to use
  • When not to use
  • Installation
  • Usage
  • API reference
  • Keyboard
  • Accessibility
  • Motion
  • Responsive behavior
  • Performance
  • Notes for AI
  • Related
View as Markdown

Talk to our team

Questions about licensing, a bug you can't pin down, or a component you wish existed. A person reads every message.

  • Replies within one business day
  • hello@example.com
Topic
500 characters left500 characters left

We reply within one business day.