Case-type intake for immigration law firms, built in GoHighLevel

The firm's spec, built as written. This firm wrote its own build instructions, down to every stage name and the rule for moving a card, and asked for them to be built exactly as written. Where anything in the spec was in conflict, we flagged it to the firm instead of settling it ourselves.

Four pipelines, one router. The build has four pipelines, New Lead, Consultations, Sales Pipeline and Customer, each with the firm's exact stages. One intake router workflow sits at the front and sends each new contact to its place.

The case-type field. Each contact carries a case-type dropdown, and every value in it has a matching tag. Messages are written per case type, so a person who asked about adjustment of status is never sent a fiancé-visa message. For a case type the firm doesn't handle, asylum for example, the contact is tagged as not a fit, moved to Not qualified or Referred out, and every workflow stops for them.

A message the moment a stage changes. When a card moves, an email and a text go out at once. Follow-up tracks, which the firm calls glidepaths, then carry on, each with a 60-minute wait written in.

The language comes from a field. Messages go out in English when the contact's preferred-language field is empty, and in Spanish when it says so. The firm wrote both versions, the Spanish in the formal usted, and in the build they are placed word for word.

Texts wait for office hours. A text goes out only between 9 AM and 7 PM Central. One that comes due outside that window is held and sent at 9:15 AM.

The morning column. At 7 AM Central, each consultation booked for that day moves into a Today's Consultations stage, so the day's meetings sit together. A person who misses their consultation goes into no-show recovery rather than dropping off the board.

Paying at booking, a contract on hire. The design books the attorney consultation through a new HighLevel booking link and takes payment as the person books, using the calendar's Charge upfront setting, which needs a payment gateway connected first. The intake form keeps its fields in one folder at the top of the contact and turns the answers into a PDF. A contract with the firm's logo goes out on hire.

Tested, not yet live. We ran the build with a test contact against the firm's own 11-point checklist, which asks for a screenshot or a note on each point. That test covered the pipelines and their stage messages. The copy, the paid booking and the intake form are built but have not run with clients, so this page describes a design, not a system in use.