Field mapping & fixed defaults

Mapping a field to your PSA/CRM

In a field's settings, enable PSA Field Binding and pick which field on the other side it corresponds to — a ticket field, a contact field, an opportunity field, whatever your connected system's picker offers. For binding to a Country or State field, you can also turn on use reference options, which pulls the live, valid option list from your PSA/CRM instead of you typing values by hand.

Fixed values for fields the visitor never sees

Not every field your PSA/CRM requires makes sense to show on a public form — a board ID, a source tag, a fixed priority. For these, use a field's Dynamic Value setting instead of PSA Field Binding:

• Custom — a hardcoded value you type once (e.g. always tag submissions with a specific campaign source).
• From URL parameter — pulls a value from the page's query string (e.g. ?ref= or ?source=), useful for tracking which page or campaign a submission came from.
• From cookie — pulls a value from a cookie already set on the visitor's browser.
• Date/time — fills in the current date or time at submission.

Every dynamic-value type except Custom also takes a fallback value, used when the URL parameter or cookie isn't present. Turn on Hide this field to keep it out of the rendered form entirely — the visitor never sees it, but the value still gets sent and mapped like any other field.