- Action ID
actions.intent.CREATE_CALL
- Description
-
Start an audio or video call. First, determine the call recipient using the
call.participant.name
orcall.participant.telephone
intent parameter. Then, determine the format (like audio or video) using thecall.callFormat
intent parameter, if available.We also recommend creating deeper, voice-forward experiences by integrating our partner solution for calling.
Locale support
Functionality | Locales |
---|---|
Preview creation using App Actions test tool | en-US |
User invocation from Google Assistant | en-US |
Example queries
Recommended fields
The following fields represent essential information that users often provide in queries that trigger this built-in intent:
call.participant.name
call.participant.telephone
Other supported fields
The following fields represent information that users often provide to disambiguate their needs or otherwise improve their results:
call.@type
call.callFormat
call.participant.@type
Supported text values by field
Inventory availability by field
Sample actions.xml
For information about the actions schema, read Create actions.xml.
Handle intent parameters as URL parameters
<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
<action intentName="actions.intent.CREATE_CALL">
<fulfillment urlTemplate="myapp://custom-deeplink{?callFormat,name,telephone}">
<!-- Eg. callFormat = "Audio" -->
<!-- (Optional) Require a field eg.callFormat for fulfillment with required="true" -->
<parameter-mapping urlParameter="callFormat" intentParameter="call.callFormat" required="true" />
<!-- Eg. name = "John Doe" -->
<parameter-mapping urlParameter="name" intentParameter="call.participant.name" />
<!-- Eg. telephone = "012-345-6789" -->
<parameter-mapping urlParameter="telephone" intentParameter="call.participant.telephone" />
</fulfillment>
<!-- Provide a fallback fulfillment with no required parameters. For example, to your app search or router deeplink -->
<fulfillment urlTemplate="myapp://deeplink" />
</action>
</actions>
Use inline inventory to guide query matching
call.callFormat
is a
field that supports inline inventory.
By defining an <entity-set>
for call.callFormat
,
you can uniquely identify entities that are of interest to your app or restrict
fulfillment to the set of supported entities.
In the following example, when the user query matches the
callFormat_one
entity, Assistant provides the associated identifier, ID_ONE
, as
the URL parameter callFormat
to fulfillment.
If there is no inventory match, the text value received in the query for
call.callFormat
is passed
as-is.
<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
<action intentName="actions.intent.CREATE_CALL">
<fulfillment urlTemplate="myapp://deeplink{?callFormat}" >
<!-- callFormat = "ID_ONE" or "ID_TWO" -->
<!-- If no inventory match, callFormat is a text value, such as "Audio" -->
<!-- (Optional) Use entityMatchRequired="true" to require inventory match for fulfillment -->
<parameter-mapping urlParameter="callFormat" intentParameter="call.callFormat" />
</fulfillment>
<!-- Define parameters with inventories here -->
<parameter name="call.callFormat">
<entity-set-reference entitySetId="callFormatEntitySet"/>
</parameter>
</action>
<entity-set entitySetId="callFormatEntitySet">
<!-- Provide an identifier per entity -->
<entity identifier="ID_ONE" name="callFormat_one" alternateName="@array/callFormat_one_synonyms"/>
<entity identifier="ID_TWO" name="callFormat_two" alternateName="@array/callFormat_two_synonyms"/>
</entity-set>
</actions>
Derive fulfillment URL using inline inventory
The url
attribute associated with the entity can be used to
determine the fulfillment URL if there is an inventory match. In the following
example, when the user query matches the
callFormat_one
entity, Assistant provides myapp://deeplink/one
as the fulfillment
URL.
<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
<action intentName="actions.intent.CREATE_CALL">
<!-- Use url from inventory match for deep link fulfillment -->
<fulfillment urlTemplate="{@url}" />
<!-- Provide a fallback fulfillment with no required parameters. For example, to your app search or router deeplink -->
<fulfillment urlTemplate="myapp://deeplink" />
<!-- Define parameters with inventories here -->
<parameter name="call.callFormat">
<entity-set-reference entitySetId="callFormatEntitySet"/>
</parameter>
</action>
<entity-set entitySetId="callFormatEntitySet">
<!-- Provide a URL per entity -->
<entity url="myapp://deeplink/one" name="callFormat_one" alternateName="@array/callFormat_one_synonyms"/>
<entity url="myapp://deeplink/two" name="callFormat_two" alternateName="@array/callFormat_two_synonyms"/>
</entity-set>
</actions>
JSON-LD sample
The following JSON-LD sample provides some example values that you can use in the App Actions test tool:
{ "@context": "http://schema.googleapis.com", "@type": "Call", "callFormat": "Audio", "participant": { "@type": "Person", "name": "John Doe", "telephone": "012-345-6789" } }