Contact Split Panel

Installation

pnpm dlx shadcn@latest add @cleverui/contact-split-panel

Requires the @cleverui registry in your components.json, a one-off, two-line setup.

Usage

tsx

import { ContactSplitPanel } from '@/components/blocks/contact-split-panel'

Exampletsx

'use client'

import { ContactSplitPanel } from '@/components/blocks/contact-split-panel'

export default function ContactSplitPanelDemo() {
  return (
    <ContactSplitPanel
      heading="Get in touch"
      intro="A person reads every message. Usually the same day, never a chatbot, never a ticket ID."
      submitLabel="Send message"
      note="Replies within one business day."
      office={{
        address: [
          'Northbeam Studio',
          '14 Flinders Lane, Level 3',
          'Melbourne VIC 3000',
          'Australia',
        ],
        phone: '+61 3 9012 4480',
        email: 'hello@northbeam.studio',
        hours: [
          { days: 'Mon – Fri', time: '9:00 – 17:30' },
          { days: 'Saturday', time: '10:00 – 14:00' },
          { days: 'Sunday', time: 'Closed' },
        ],
      }}
      onSubmit={() => {
        // demo settles success state via the component
      }}
    />
  )
}

API reference

ContactSplitPanel accepts the following props.

Prop	Type	Default	Description
`heading`	`string`	`'Get in touch'`	–
`intro`*	`string`	–	one honest sentence, e.g. 'A person reads every message. Usually the same day.'
`onSubmit`*	`(data: { name: string; email: string; message: string }) => void`	–	–
`submitLabel`	`string`	`'Send message'`	–
`office`*	`ContactOffice`	–	–
`note`	`string`	`'Replies within one business day.'`	mono reassurance line under the submit button
`headingLevel`	`2 \| 3`	`2`	–

…plus everything from Omit<React.HTMLAttributes<HTMLElement>, 'onSubmit'>: className, event handlers, aria attributes and the rest pass straight through.

Referenced types

Typestsx

export interface ContactOffice {
  address?: string[]
  phone?: string
  email?: string
  /** preformatted strings, e.g. { days: 'Mon - Fri', time: '9:00 - 17:30' } */
  hours?: ContactOfficeHours[]
}

export interface ContactOfficeHours {
  days: string
  time: string
}

Related components

Contact Callback Strip

Slim request-a-callback band in React, one tel field, a morning or afternoon window picker and an honest callback promise, collapsing to a confirmation. Tailwind micro form.

Contact Project Brief

Project inquiry form that composes a brief, radio-chip fieldsets for type, budget and timeline with a live mono summary line. An honest React and Tailwind contact form for agencies.

Contact Channel Cards

Pick-your-channel contact tiles, email, call, visit, each a working link with a quiet response-time promise; the single recommended channel carries the primary keyline.

Contact Email Spotlight

Minimal contact block that commits to one channel, the email address set at display scale as a working mailto with copy-to-clipboard and a quiet response promise. React + Tailwind.

Contact Split Map

Contact section with a token-drawn SVG map, abstract street grid, primary pin, office switcher, and working tel, mailto and directions links. React + Tailwind, no map embed.

Split Button

A self-contained split button for React, filled primary action, hairline-divided menu toggle, and real role=menu keyboard semantics with zero Radix or portal dependencies.

Frequently asked questions

How do I install the Contact Split Panel component?

Register the @cleverui registry in your components.json ("@cleverui": "https://cleverops.com.au/r/{name}.json"), then run `npx shadcn@latest add @cleverui/contact-split-panel`. The shadcn CLI copies the source into your project, you own the code from that point. You can also copy the source directly from this page.

What dependencies does Contact Split Panel require?

Contact Split Panel uses motion and lucide-react on top of React and Tailwind CSS. You don't need to install them manually, the shadcn CLI resolves and installs npm dependencies automatically when you add the component.

Can I theme Contact Split Panel to match my brand?

Yes. The component is styled entirely with Tailwind utilities over standard design tokens (primary, background, muted, border), so it inherits your existing shadcn/ui theme automatically. Change your CSS variables and the component follows, no source edits needed for palette, radius, or fonts.

Preview & code