Summary
CreateCustomerContactRequest exposes only customerId, so a client can create a contact but can't attach anything to it — no caseRef (to scope it to a case), no type (ContactType), no plannedTime/state (to schedule an appointment), no note/representative. The read side already supports caseRef, so create/read are asymmetric.
Verified (@insurup/contracts@0.1.26, dist/customers.d.ts)
CreateCustomerContactRequest L601–603 → { customerId: string } — nothing else.- Read requests carry
caseRef: GetCustomerContactsRequest L621–624 and GetCustomerContactFlowsRequest L614–617 (both { customerId, caseRef?: string | null }).
- The read model is rich (
GetCustomerContactsResultItem ~L773+): type, state, plannedTime, attemptTime, …
ContactType L95–97 has only PhoneCall; ContactState L103–109 = Planned | Occurred | NotOccurred. So an "appointment/randevu" is modelled as a Planned contact with a plannedTime — but the create request can set none of these.
Impact
Blocks creating a case-scoped contact and scheduling an appointment from the client. In agent-panel this left the case-detail Communications tab's "Add contact" / "Add appointment" actions unbuildable.
Proposed fix
Extend CreateCustomerContactRequest (and the endpoint contract) to accept at least caseRef?, type (ContactType), state/plannedTime (scheduled contacts), and optional note/representative — matching the fields the read model already returns. Please confirm the authoritative field list against the Core create-contact command.
Context: surfaced during the agent-panel Cases (Talepler) module migration (InsurUp/agent-panel#8).
Summary
CreateCustomerContactRequestexposes onlycustomerId, so a client can create a contact but can't attach anything to it — nocaseRef(to scope it to a case), notype(ContactType), noplannedTime/state(to schedule an appointment), no note/representative. The read side already supportscaseRef, so create/read are asymmetric.Verified (@insurup/contracts@0.1.26, dist/customers.d.ts)
CreateCustomerContactRequestL601–603 →{ customerId: string }— nothing else.caseRef:GetCustomerContactsRequestL621–624 andGetCustomerContactFlowsRequestL614–617 (both{ customerId, caseRef?: string | null }).GetCustomerContactsResultItem~L773+):type,state,plannedTime,attemptTime, …ContactTypeL95–97 has onlyPhoneCall;ContactStateL103–109 =Planned | Occurred | NotOccurred. So an "appointment/randevu" is modelled as aPlannedcontact with aplannedTime— but the create request can set none of these.Impact
Blocks creating a case-scoped contact and scheduling an appointment from the client. In agent-panel this left the case-detail Communications tab's "Add contact" / "Add appointment" actions unbuildable.
Proposed fix
Extend
CreateCustomerContactRequest(and the endpoint contract) to accept at leastcaseRef?,type(ContactType),state/plannedTime(scheduled contacts), and optional note/representative — matching the fields the read model already returns. Please confirm the authoritative field list against the Core create-contact command.Context: surfaced during the agent-panel Cases (Talepler) module migration (InsurUp/agent-panel#8).