ContactPoint - schema.org

# schema.org

- Documentation
- Schemas
- Home

# ContactPoint

#### Thing > Intangible > StructuredValue > ContactPoint

A contact point—for example, a Customer Complaints department.
Usage: Between 10,000 and 50,000 domains

Property | Expected Type | Description
--- | --- | ---
[more...]

- Leave public feedback on this term 💬
- Check for open issues.
- 'ContactPoint' is mentioned in layer: core
- 'ContactPoint' is mentioned in extension layer: pending

Properties from ContactPoint
`areaServed` | AdministrativeArea or GeoShape or Place or Text | The geographic area where a service or offered item is provided. Supersedes serviceArea.
`availableLanguage` | Language or Text | A language someone may use with the item. Please use one of the language codes from the IETF BCP 47 standard. See also inLanguage.
`contactOption` | ContactPointOption | An option available on this contact point (e.g. a toll-free number or support for hearing-impaired callers).
`contactType` | Text | A person or organization can have different contact points, for different purposes. For example, a sales contact point, a PR contact point and so on. This property is used to specify the kind of contact point.
`email` | Text | Email address.
`faxNumber` | Text | The fax number.
`hoursAvailable` | OpeningHoursSpecification | The hours during which this service or contact is available.
`productSupported` | Product or Text | The product or service this support contact point is related to (such as product support for a particular product line). This can be a specific product or product line (e.g. "iPhone") or a general category of products or services (e.g. "smartphones").
`telephone` | Text | The telephone number.
Properties from Thing
`additionalType` | URL | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.
`alternateName` | Text | An alias for the item.
`description` | Text | A description of the item.
`disambiguatingDescription` | Text | A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.
`image` | ImageObject or URL | An image of the item. This can be a URL or a fully described ImageObject.
`mainEntityOfPage` | CreativeWork or URL | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details. Inverse property: mainEntity.
`name` | Text | The name of the item.
`potentialAction` | Action | Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
`sameAs` | URL | URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Freebase page, or official website.
`url` | URL | URL of the item.

Instances of ContactPoint may appear as values for the following properties

Property | On Types | Description
--- | --- | ---
`contactPoint` | Organization or Person | A contact point for a person or organization. Supersedes contactPoints.
`grantee` | DigitalDocumentPermission | The person, organization, contact point, or audience that has been granted this permission.
`homeLocation` | Person | A contact location for a person's residence.
`servicePhone` | ServiceChannel | The phone number to use to access the service.
`serviceSmsNumber` | ServiceChannel | The number to access the service by text message.
`workLocation` | Person | A contact location for a person's place of work.

More specific Types

- PostalAddress

Examples
Example 1
Without Markup Microdata RDFa JSON-LD

    This example shows a JSON-LD description of services that do not necessarily have a direct
    human-oriented HTML description. It describes a GovernmentService named "Veterans Affairs Emergency Mental Health",
    its operator, service area and service details, such as its Veterans Crisis Line (including  phone contact line
    hours of operation, language and other details).

    This example is JSON only.

    This example is JSON only.

    <script type='application/ld+json'>
    {
      "@context": "http://schema.org",
      "@type": "GovernmentService",
      "name": "Veterans Affairs Emergency Mental Health",
      "serviceType": "Psychiatric Emergency Services",
      "operator": {
        "@type": "GovernmentOrganization",
        "name": "US Department of Veterans Affairs"
      },
      "serviceArea": {
        "@type": "AdministrativeArea",
        "name": "Massachusetts"
      },
      "audience": {
        "@type": "CivicAudience",
        "name": "Veterans"
      },
      "availableChannel": {
        "@type": "ServiceChannel",
        "name": "Urgent Care Clinic",
        "availableLanguage": {
          "@type": "Language",
          "name": "Spanish",
          "alternateName": "es"
        },
        "serviceLocation": {
          "@type": "Hospital",
          "name": "VA Boston -- West Roxbury",
          "address": {
            "@type": "PostalAddress",
            "streetAddress": "1400 VFW Parkway",
            "addressLocality": "West Roxbury",
            "addressRegion": "MA",
            "postalCode": "02132"
          }
        }
      }
    }
    </script>

Example 2
Without Markup Microdata RDFa JSON-LD

    Example specifying one customer service phone number.

    This example is JSON-only.

    This example is JSON-only.

    <script type="application/ld+json">
    { "@context" : "http://schema.org",
      "@type" : "Organization",
      "url" : "http://www.your-company-site.com",
      "contactPoint" : [
        { "@type" : "ContactPoint",
          "telephone" : "+1-401-555-1212",
          "contactType" : "customer service"
        } ] }
    </script>

Example 3
Without Markup Microdata RDFa JSON-LD

    A fuller example that illustrates multiple contact numbers for a company,
    including US toll-free numbers, a hearing-impaired number, and several contact categories.

    This example is JSON-only.

    This example is JSON-only.

    <script type="application/ld+json">
    { "@context" : "http://schema.org",
      "@type" : "Organization",
      "url" : "http://www.t-mobile.com",
      "contactPoint" : [
        { "@type" : "ContactPoint",
          "telephone" : "+1-877-746-0909",
          "contactType" : "customer service",
          "contactOption" : "TollFree",
          "areaServed" : "US"
        } , {
          "@type" : "ContactPoint",
          "telephone" : "+1-505-998-3793",
          "contactType" : "customer service"
        } , {
          "@type" : "ContactPoint",
          "telephone" : "+1-877-296-1018",
          "contactType" : "customer service",
          "contactOption" : ["HearingImpairedSupported","TollFree"] ,
          "areaServed" : "US"
        } , {
          "@type" : "ContactPoint",
          "telephone" : "+1-877-453-1304",
          "contactType" : "technical support",
          "contactOption" : "TollFree",
          "areaServed" : ["US","CA"],
          "availableLanguage" : ["English","French"]
        } , {
          "@type" : "ContactPoint",
          "telephone" : "+1-877-453-1304",
          "contactType" : "bill payment",
          "contactOption" : "TollFree",
          "areaServed" : ["US","CA"]
        } ] }
    </script>

Schema Version 3.0