Consider including contactPoint in the model for an Organization when specified as a customer. Otherwise there is no means specified to capture the contact details of the Organization.
For example the following:
{
"@type": "Organization",
"name": "Company Limited",
"address": {
"@type": "PostalAddress",
"streetAddress": "Raynes Park High School, 46A West Barnes Lane",
"addressLocality": "New Malden",
"addressRegion": "London",
"postalCode": "NW5 3DU",
"addressCountry": "GB"
},
"contactPoint": {
"@type": "ContactPoint",
"name": "Ralph Jones",
"email": "alexjones@example.com",
"telephone": "020 811 8055"
}
}
Open question: although the model above comes out-of-the-box with schema.org, should this instead include a Person object as the primaryContact or similar rather than a ContactPoint (which is not intended for details of a specific person)
For systems that require a Person to be associated with the Organization rather than just a contact centre number, primaryContact is likely a more accurate model. However if a contact centre contract is preferred for a B2B relationship, perhaps contactPoint would be preferred.
Implementation experience may be required here.
Consider including
contactPointin the model for anOrganizationwhen specified as acustomer. Otherwise there is no means specified to capture the contact details of theOrganization.For example the following:
Open question: although the model above comes out-of-the-box with schema.org, should this instead include a
Personobject as theprimaryContactor similar rather than aContactPoint(which is not intended for details of a specific person)For systems that require a
Personto be associated with theOrganizationrather than just a contact centre number,primaryContactis likely a more accurate model. However if a contact centre contract is preferred for a B2B relationship, perhapscontactPointwould be preferred.Implementation experience may be required here.