Language selection

Search

Patent 2714435 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent: (11) CA 2714435
(54) English Title: SYSTEM AND METHOD FOR DEEP DIALING PHONE SYSTEMS
(54) French Title: SYSTEME ET PROCEDE POUR SYSTEMES DE MENU TELEPHONIQUE
Status: Granted
Bibliographic Data
(51) International Patent Classification (IPC):
  • H04M 3/42 (2006.01)
  • H04M 3/428 (2006.01)
  • H04M 3/533 (2006.01)
  • H04M 11/10 (2006.01)
(72) Inventors :
  • BERGER, SHAI (Canada)
  • BIGUE, JASON P. (Canada)
  • PULTZ, MICHAEL (Canada)
(73) Owners :
  • FONCLOUD INC. (Canada)
(71) Applicants :
  • FONCLOUD INC. (Canada)
(74) Agent: OPEN IP CORPORATION
(74) Associate agent:
(45) Issued: 2017-11-21
(86) PCT Filing Date: 2009-03-10
(87) Open to Public Inspection: 2009-09-17
Examination requested: 2014-02-28
Availability of licence: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): Yes
(86) PCT Filing Number: PCT/US2009/036613
(87) International Publication Number: WO2009/114501
(85) National Entry: 2010-08-24

(30) Application Priority Data:
Application No. Country/Territory Date
61/035,204 United States of America 2008-03-10
61/035,195 United States of America 2008-03-10

Abstracts

English Abstract




An independent communications
system (ICS) is used in a
transaction between waiting party and
a queuing party, with the queuing party
having a interactive voice response
(IVR). The IVR includes multiple
nodes and the ICS is adapted to connect
to a particular node in the IVR.




French Abstract

Un système de communication indépendant (independent communications system/ICS) est utilisé au cours d'une transaction entre une partie en attente et une partie de mise en file d'attente, l'intervenant de misse en file d'attente étant équipé d'un système de réponses vocales interactif (Interactive Voice response/IVR). Le système IVR comprend des noeuds mutliples et le système ICS est conçu pour se connecter sur un noeud particulier des système IVR.

Claims

Note: Claims are shown in the official language in which they were submitted.


10
1. An independent communication system (ICS) used in a transaction between a
waiting
party and a queuing party, the queuing party having an interactive voice
response (IVR),
the IVR having a plurality of nodes, the ICS operating independently of the
queuing
party to receive a request from the waiting party to connect to a particular
node in the
IVR using DTMF tones, voice cues, and software commands in combination with an
IVR
map that is separate from the 1VR of the queuing party to navigate to the
particular node
in the IVR independently from the queuing party.
2. The ICS of claim 1, further configured to receive a specific voice address
and a
request from the waiting party to connect to a particular node, and to
facilitate
connecting the waiting party via a call back to the specific voice address, to
the
particular node in the IVR.
3. The ICS of any one of claims 1 or 2, wherein the ICS is adapted to call the
waiting
party prior to a last step in navigating the IVR map.
4. The ICS of any one of claims 1 to 3, wherein the ICS is adapted to inform
the waiting
party of the status of the transaction via at least one of graphical
presentation, text, and
audio.
5. The ICS of any one of claims 1 to 4, wherein the ICS is adapted to generate

aggregate statistics about a queuing party, the aggregate statistics
comprising at least
one of popular node or nodes, average hold time to connect to a node, call
volume, call
duration, and optimal time to schedule a call.
6. The ICS of claim 5, wherein the ICS is further adapted to display or inform
the
aggregate statistics.
7, The ICS of any one of claims 1 to 6, wherein the ICS is adapted to
automatically
select an appropriate voice address of the waiting party.

11
8. The ICS of any one of claims 2 to 7, wherein the ICS is adapted to select
the voice
address based on profile information about the waiting party.
9. An independent communication system (ICS) used in a transaction between a
waiting
party and a queuing party, the queuing party having an interactive voice
response
(IVR), the IVR having a plurality of nodes, the ICS adapted to receive an
advance
schedule calling request from the waiting party to connect to a particular
node, and to
facilitate connecting the waiting party to the particular node in the IVR
according to the
advance schedule calling request, using at least one of DTMF tones, voice
cues, and
software commands in combination with an IVR map that is separate from the IVR
of
the queuing party to navigate to the particular node in the IVR.
10. The ICS of claim 9, wherein the ICS is adapted to facilitate connecting
the waiting
party to the particular node in the IVR according to the advance schedule
calling
request, using DTMF tones, voice cues, and software commands in combination
with an
IVR map that is separate from the IVR of the queuing party to navigate to the
particular
node in the IVR.
11. A communication system (CS) used in a transaction between a waiting party
and a
queuing party, wherein the queuing party includes an interactive voice
response (IVR),
and wherein the IVR includes a plurality of nodes, the CS adapted to present a

graphical presentation of the IVR to the waiting party, receive a request from
a device
used by the waiting party to connect the device to a particular node prior to
the
transaction taking place, and connect the waiting party to the particular node
in the IVR,
using at least one of voice cues and DTMF tones, in combination with an IVR
map to
navigate to the particular node in the IVR, wherein the waiting party is not
required to
have previously interacted with the queuing party.

12
12. The CS of claim 11, wherein the CS is adapted to connect the waiting
party to
the particular node in the IVR, using DTMF tones, voice cues, and software
commands
in combination with an IVR map to navigate to the particular node in the IVR,
wherein
the waiting party is not required to have previously interacted with the
queuing party.
13. The CS of any one of claims 11 to 12, wherein the CS is further adapted to
inform
the waiting party of a connection or an imminent connection to the particular
node.
14. The CS of any one of claims 11 to 13, wherein the IVR map is separate from
the
IVR of the queuing party.
15. A method used in a transaction between a waiting party and a queuing
party, the
queuing party having an interactive voice response (IVR), the IVR having a
plurality of
nodes, the method comprising operating independently of the queuing party to
receive a
request from the waiting party to connect to a particular node prior to the
transaction
taking place, and facilitating to connect the waiting party to the particular
node in the
IVR using at least one of DTMF tones, voice cues, and software commands in
combination with an IVR map that is separate from the IVR of the queuing party
to
navigate to the particular node in the IVR independently from the queuing
party.
16. The method of claim 15, wherein the facilitating to connect the waiting
party to the
particular node in the IVR uses voice cues and DTMF tones in combination with
an IVR
map that is separate from the IVR of the queuing party to navigate to the
particular node
in the IVR independently from the queuing party
17. The method of any one of claims 15 to 16, further comprising calling the
waiting
party about the same time or prior to a last step in navigating the IVR map.
18. The method of any one of claims 15 to 17, further comprising informing the
waiting
party of the status of the transaction via at least one of graphical
presentation, text, and

13
audio.
19. The method of any one of claims 15 to 18, further comprising generating
aggregate
statistics about a queuing party, the aggregate statistics comprising at least
one of
popular node or nodes, average hold time to connect to a node, call volume,
call
duration, and optimal time to schedule a call.
20. The method of claim 19, further displaying or informing the aggregate
statistics.
21. The method of any one of claims 15 to 20, further comprising automatically

selecting an appropriate voice address of the waiting party.
22. The method of any one of claims 15 to 21, further comprising selecting the
voice
address based on profile information about the waiting party.
23. The method of any one of claims 15 to 22, further comprising receiving a
specific
voice address and a request from the waiting party to connect to a particular
node in the
IVR, and facilitating connecting the waiting party via a call back to the
specific voice
address, to the particular node in the IVR.
24. A method used in a transaction between a waiting party and a queuing
party, the
queuing party having an interactive voice response (IVR), the IVR having a
plurality of
nodes, the method comprising receiving a specific voice address and a request
from the
waiting party to connect to a particular node in the IVR, and facilitating
connecting the
waiting party via a call back to the specific voice address, to the particular
node in the
IVR, using at least one of DTMF tones, voice cues, and software commands in
combination with an IVR map that is separate from the IVR of the queuing party
to
navigate to the particular node in the IVR.

14
25. The method of claim 24, wherein the facilitating connecting the waiting
party via a
call back to the specific voice address, to the particular node in the IVR,
uses DTMF
tones, voice cues, and software commands in combination with an IVR map that
is
separate from the IVR of the queuing party to navigate to the particular node
in the IVR.
26. The method of any one of claims 24 to 25, further comprising calling the
waiting
party about the same time or prior to a last step in navigating the IVR map.
27. A method used in a transaction between a waiting party and a queuing
party,
wherein the queuing party includes an interactive voice response (IVR), and
wherein the
IVR includes a plurality of nodes, the method comprising presenting at least a
section
menu of the plurality of nodes of the IVR to a device used by the waiting
party prior to
the transaction taking place to allow the waiting party to select a particular
node in the
IVR, further facilitating connecting the device to the particular node in the
IVR using at
least one of_DTMF tones, voice cues, and software commands in combination with
an
IVR map to navigate to the particular node in the IVR, wherein the waiting
party is not
required to have previously interacted with the queuing party.
28. The method of claim 27, further receiving a request from the waiting
party to
connect to a particular node in the IVR.
29. The method of any one of claims 27 to 28, further facilitating
connecting the
waiting party to the particular node in the IVR.
30. The method of claim claims 27 to 29, further comprising informing the
waiting
party of a connection or an imminent connection to the particular node.
31. A method used in a transaction between a waiting party and a queuing
party,
wherein the queuing party includes an interactive voice response (IVR), and
wherein the
IVR includes a plurality of nodes, the method comprising:

15
presenting a graphical user interface displaying a plurality of nodes from the
IVR to the
waiting party;
receiving from a device used by the waiting party a selection of a particular
node of the
plurality of nodes from the waiting party; and
facilitating connecting the device to the particular node in the IVR using at
least one of
voice cues, DTMF tones, and software, in combination with an IVR map that is
separate
from the IVR of the queuing party to navigate to a particular node in the IVR,
wherein
the waiting party is not required to have previously interacted with the
queuing party.
32. The method of claim 31, wherein the facilitating connecting the device
to the
particular node in the IVR uses DTMF tones, voice cues, and software commands
in
combination with an IVR map that is separate from the IVR of the queuing party
to
navigate to a particular node in the IVR
33. A method used in a transaction between a waiting party and a queuing
party,
wherein the queuing party includes an interactive voice response (IVR), and
wherein the
IVR includes a plurality of nodes, the method comprising connecting a device
used by
the queuing party to a particular node in the IVR using at least one of DIME
tones,
voice cues, and software commands in combination with an IVR map and to
navigate to
the particular node in the IVR and informing the waiting party of a status of
the
transaction via one of graphical presentation or text to the device, wherein
the waiting
party is not required to have previously interacted with the queuing party.
34. The method of claim 33, further comprising informing the waiting party
of a
connection or imminent connection through a computing or mobile device.
35. A method used in a transaction between a waiting party and a queuing
party,
wherein the queuing party includes an interactive voice response (IVR), and
wherein the
IVR includes a plurality of nodes, the method comprising connecting a device
used by
the queuing party to a particular node in the IVR using at least one of voice
cues and

16
DTMF tones, in combination with an IVR map that is separate from the IVR of
the
queuing party and to navigate to the particular node in the IVR and informing
the waiting
party of a status of the transaction via one of graphical presentation or text
to the
device, wherein the waiting party is not required to have previously
interacted with the
queuing party.
36. The method of claim 35, further comprising informing the waiting party of
a
connection or imminent connection through a computing or mobile device.

Description

Note: Descriptions are shown in the official language in which they were submitted.



CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
SYSTEM AND METHOD FOR DEEP DIALING PHONE SYSTEMS

Field of Invention
The present invention relates to the field of communication call management,
and, more particularly, to automated call completion and automated IVR
interaction and
related methods.

Background of the Invention
Today, when a user (a waiting party) calls a large company or service center
or
(a queuing party), it is very likely that he or she will be connected to an
interactive voice
response (IVR) system. Such systems present the waiting party with information
via a
series of queues such as audio prompts and get input from the caller, via dial
tone multi-
frequency (DTMF) tones (also known as "touch tones") or verbal commands. It is
very
desirable to provide a communication system and method which allows a waiting
party
(the waiting party) to reach a particular point in an IVR system directly,
that is, without
navigating through the menu hierarchy to reach that point. In the present
disclosure, this
process is referred to as "deep dialing". Such systems may also be referred to
as
"phone menus" or "phone trees".

Summary of the Invention
Embodiments of the present invention provide in one aspect an independent
communication system (ICS) used in a transaction between a waiting party and a
queuing party, the queuing party having a interactive voice response (IVR),
the IVR
having a plurality of nodes, the ICS adapted to connect to a particular node
in the IVR.
In another aspect, the present embodiments provide a method used in a
transaction between a waiting party and a queuing party, the queuing party
having a


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
2
interactive voice response (IVR), the IVR having a plurality of nodes, the
method
comprising enabling the waiting party to connect to a particular node in the
IVR.

Brief Description of the Drawings
For a fuller understanding of the invention, reference is made to the
following
detailed description, taken in connection with the accompanying drawings
illustrating
various embodiments of the present invention, in which;
FIG. 1 is an illustration of an exemplary IVR map;
FIG. 2 is an illustration of a communications system that incorporates an
exemplary embodiment related to IVR mapping and deep dialing:
FIG. 3 is an illustration of a communications system that incorporates an
exemplary embodiment audio device is an "IP-based" phone;
FIG. 4 is an illustration of a communications system that incorporates an
illustrative embodiment in which the role of the data device is replaced by an
IVR
system;
FIG. 5 is an illustrative timeline describing a typical transaction using a
system
built according to an exemplary embodiment; and
FIG. 6 is an illustration of a call status report generated according to an
exemplary embodiment.

Detailed Description of the Preferred Embodiments
The present invention will now be described more fully hereinafter with
reference
to the accompanying drawings, in which preferred embodiments of the invention
are
shown. This invention may, however, be embodied in many different forms and
should
not be construed as limited to the embodiments set forth herein. Rather, these
embodiments are provided so that this disclosure will be thorough and
complete, and
will fully convey the scope of the invention to those skilled in the art. Like
numbers refer
to like elements throughout, and prime notation is used to indicate similar
elements in
alternate embodiments.


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
3
The embodiments presented herein provide a system and method which allows
the waiting party to dial into a particular node in the IVR map used by a
queuing calling
system (QCS) of a queuing party in a transaction which might be through a
landline
phone, mobile phone, web-based phone, softphone, and the like.
An "IVR map" is a structured list of all the possible paths through a given
IVR
system, where each path consists of one or more nodes. Figure 1 shows an
illustrative
example of such an IVR map. Each node in an IVR map represents a specific
point in a
tree-like structure where the waiting party may be prompted to send a command
by
entering data, e.g. via punching in numbers on a dial pad, or spelling out
commands
verbally, etc. The result of this action by the waiting party advances him or
her onto the
next node and so on and so forth in order to eventually reach a node through
which he
or she could execute an originally intended function.
Accordingly, each node in the map includes a prompt and possibly one or more
commands. The prompt is, for example, the audio that is heard by the caller
and is
represented in the map by the corresponding text. Each command can be a DTMF
tone
or a verbal command and allows the caller to navigate to another node in the
IVR
system, or will put the caller in a queue to speak to a live agent.
The strength of the IVR system is its universality. It works on any phone and
is
usable by even the least technically inclined people. IVR systems are favored
by a
queuing party because they allow live agents to be used more effectively,
which in turn
reduces the costs of running call centers. Recent advances in technology are
making
IVR systems both easier to set up and more elaborate. Customer interactions
that used
to involve a live agent (by way of example, checking a bank balance or making
a
payment) are being delegated more and more to the "automated attendant". It's
clear
that IVRs will be in wide use around the world at least for the foreseeable
future.
However, IVR systems can be very frustrating to the waiting party. By way of
example:
1. Queuing parties are putting more and more marketing messages
into their IVRs, which may provide no value to the waiting party and
increases the time it takes him or her to accomplish his objective.


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
4
2. For very long menus, it can be hard for the waiting party to
remember all the options by the time the menu completes.
3. Often the waiting party simply wants to speak to a live agent, but
the path to get there is not obvious. In fact, sometimes queuing parties
make reaching an agent deliberately obtuse.
The embodiments presented herein provide a communications system and
corresponding method. In some embodiments, the method includes receiving a
request
from a waiting party to call a particular node of a particular IVR system of a
particular
party (the queuing party). The queuing party is then called and sent
appropriate
commands (e.g. DTMF tones or voice cues) such that the desired node of the IVR
map
is reached. When the requested node is detected, the waiting party is called
or
informed, at a phone number or generally at a voice address (or other real-
time
communication address previously indicated by the waiting party or known by
the
system), and connected to the queuing party.
The embodiments presented herein bring advantages to the waiting party by
removing the need to listen and chose through unnecessary nodes in the IVR
map. The
waiting party may also save money from the reduced phone time (especially if
the
waiting party is using a mobile phone). Furthermore, the embodiments presented
herein
imply no explicit cost or effort to the queuing party.
Figure 2 shows an illustrative communications system that incorporates an
exemplary embodiment. The waiting party I interacts with a data device 2 for
controlling
an independent calling system (ICS) and receiving information from it. The
data device
could be embodied as a web site on a PC or mobile device, which interacts with
the ICS
3 through a data network such as internet. The waiting party also interacts
with an audio
device 4 for real-time audio communication with the queuing party over a real-
time
audio communication network 5. The audio device could be a fixed-line or
wireless
telephone (alternatively an IP/web/internet-based phone or softphone). The
real-time
audio communication network could be the public switched telephone network
(PSTN)
(alternatively a wireless network, the internet, or an LAN/WAN). Typically the
queuing
party is a large company or a service center, but in some embodiments, this
may not be


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
the case. An IVR database 6 stores IVR maps that allow the ICS to navigate the
IVR
properly.
Figure 3 illustrates another communications system that incorporates an
exemplary embodiment. In this embodiment, the audio device is an
"IP/web/internet-
5 based" phone, meaning that it communicates over a packet-based network, such
as
internet. The audio device in this case, may also be a softphone that operates
as
software on a computer. It is further possible that the audio device is a
softphone
operating on the waiting party's data device, so that one device fills the
roles of both
audio device and data device.
Figure 4 illustrates yet another communications system that incorporates an
exemplary embodiment. In this embodiment, the role of the data device is
replaced by
an IVR system, operated by the ICS (a separate IVR from that of the queuing
party). In
this embodiment, the waiting party controls the ICS and receives data from it
through an
audio device, using commands such as DTMF tones or voice cues. In this
embodiment,
one device fills the roles of both audio device and data device.
The Voice Address
In some embodiments, the waiting party must specify a voice address (a phone
number, a SIP address, web/internet-based phone address, etc.) that allows
real-time
two-way audio communication between the waiting party and the ICS. In some
embodiments, the voice address is selected automatically based on information
about
the waiting party (such as the last voice address he or she used) stored in a
database
accessible by the ICS and/or information that identify the data device (such
an IP
address or a browser cookie).
Typical Transaction
Figure 5 illustrates a timeline describing a typical transaction using a
system built
according to an exemplary embodiment. The system is further elaborated below,
where
the numbers correspond to the steps in Figure 5 and inlcude:
1. The transaction begins when a waiting party makes a request to the
ICS, through the data device. to place a call to the queuing party, and
reach a particular node in their IVR map.


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
6

2. The ICS dials the queuing party, e.g. over the PSTN, and connects
to the QCS.
3. The ICS sends to the QCS the commands required to navigate the
IVR map to the requested node. These commands could be DTMF tone.
voice cues, software commands, etc.
4. The ICS dials the waiting party using the information he or she
provided in step 1. In certain embodiments, this step is not necessary.
5. When the waiting party answers, he or she is connected to the
CCS, and can interact with the CCS normally.
Reporting Status to the Waiting Party
In some embodiments, the ICS can report the status of the call (transaction)
to
the waiting party in a variety of ways. In embodiments where the data device
has a
visual interface (e.g. on a PC, mobile device, multi-media device etc.), the
status may
be displayed via graphical presentation as shown in Figure 6. The data
reported may
include the "state" of the transaction (which may indicate, for example, which
stage of
the timeline from Figure 5 is current). In other embodiments, this information
could be
reported as audio or plain text.
Collecting aggregate statistics
As the ICS is used by many waiting parties over a period of many days, it is
possible for aggregate statistics to be collected about some queuing parties,
such as
which nodes are more popular than others. Other useful statistics could
include average
hold time to connect to a node, call volume, call duration, and optimal time
to schedule
a call.
Pre-dialing
One issue that needs to be addressed regarding the procedures described above
in typical transaction, as illustrated in Figure 5, is that the waiting party
may not be able
to hear the beginning of the prompt of the node he or she has requested. This
is
because it takes time for the ICS to establish the connection through the
audio device
(e.g. in the case where the audio device is a telephone, it takes time to
reach the phone
and press the appropriate key to accept the call.) In some embodiments, the
ICS
addresses this problem by dialing the waiting party prior to the last step in
navigating


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
7

the IVR map. Accordingly, when the connection is established, the ICS sends
the
command to perform the final navigation. This approach allows the waiting
party to hear
the prompt for the requested node in its entirety.
The waiting party can change his or her voice address.
In some embodiments, the ICS can allow the waiting party to change the voice
address after the call request has been initiated. In certain embodiments,
this change
may be possible at any point up to step 4 in Figure 5. In the embodiments
where the
data device has a visual interface (e.g. on a PC or mobile device), this
process could be
initiated by clicking a button (e.g. "Change voice address") as shown in
Figure 6. In
other embodiments, this interaction may be voice-based or text-based.
The waiting party can cancel the call.
In some embodiments, the ICS can allow the waiting party to cancel the call
after
the call request has been initiated. In certain embodiments, this change may
be
possible at any point up to step 4 in Figure 5. In embodiments where the data
device
has a visual interface (e.g. on a PC or mobile device), this process could be
initiated by
clicking a button (e.g. "Cancel Call") as shown in Figure 6. In other
embodiments, this
interaction may be voice-based or text-based.
Other functions may include the waiting party requesting the handoff of the
call to
another party, or could place an advance scheduled calling, or change the
voice
address at which he or she desired to be reached. First two functions could
take place
via proper arrangement or programming prior to the ICS reaching the desired
node and
calling back the waiting party. The advance scheduled calling accommodates the
waiting party's plans.
One advantage and feature of the embodiments presented herein is to provide a
communication system and method which allow a waiting party to connect
directly to a
point inside the IVR System of a particular queuing party. The IVR system of
the
queuing party combined with any other communication systems of the queuing
party are
referred to herein as the queuing communication system (QCS). In this context
connecting "directly" means that the waiting party does not have to enter any
commands to navigate the IVR map. This process is referred to as deep dialing,
in that
it allows the waiting party to connect "deep" into the IVR menu.


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
8
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that requires no changes to the QCS.
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that is transparent to the queuing
party,
requires no negotiation with the queuing party and requires no cooperation
from the
queuing party.
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that provides real-time, or near
real-time,
feedback to the waiting party about the status of his call.
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that allows the waiting party,
queuing party,
or a third party to collect aggregate statistics such as the most commonly
requested
nodes in a particular IVR map. Such aggregate statistics could include popular
nodes,
average hold time to connect to a node, call volume, call duration, and an
optimal time
to schedule a call.
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that allows the waiting party to
specify a
voice address (typically a phone number but also potentially a SIP address,
web-based
phone address, etc.) that allows real-time two-way audio communication where
he or
she can be reached and allows the waiting party to change the voice address
while the
deep dialing call is in progress.
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that automatically selects an
appropriate
voice address based on profile information stored about the waiting party or
other
information.
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that allows the waiting party to
cancel the
deep dialing call.
Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that allows the waiting party to
change his
or her voice address, or hand off to a third party during the deep dialing
process.


CA 02714435 2010-08-24
WO 2009/114501 PCT/US2009/036613
9

Another advantage and feature of the embodiments presented herein is to
provide such a system and method in a way that allows the waiting party to
arrange or
program for advance scheduled calling of a particular node in an IVR menu.
Many modifications and other embodiments of the invention will come to the
mind of one skilled in the art having the benefit of the teachings presented
in the
foregoing descriptions and associated drawings. Therefore, it is understood
that the
invention is not to be limited to the specific embodiments disclosed, and that
modifications and embodiments are intended to be included within the scope of
the
appended claims.

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Administrative Status , Maintenance Fee  and Payment History  should be consulted.

Administrative Status

Title Date
Forecasted Issue Date 2017-11-21
(86) PCT Filing Date 2009-03-10
(87) PCT Publication Date 2009-09-17
(85) National Entry 2010-08-24
Examination Requested 2014-02-28
(45) Issued 2017-11-21

Abandonment History

There is no abandonment history.

Maintenance Fee

Last Payment of $253.00 was received on 2024-02-26


 Upcoming maintenance fee amounts

Description Date Amount
Next Payment if standard fee 2025-03-10 $624.00
Next Payment if small entity fee 2025-03-10 $253.00

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Patent fees are adjusted on the 1st of January every year. The amounts above are the current amounts if received by December 31 of the current year.
Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Payment History

Fee Type Anniversary Year Due Date Amount Paid Paid Date
Application Fee $200.00 2010-08-24
Registration of a document - section 124 $100.00 2010-11-09
Maintenance Fee - Application - New Act 2 2011-03-10 $50.00 2010-11-09
Maintenance Fee - Application - New Act 3 2012-03-12 $50.00 2012-03-01
Maintenance Fee - Application - New Act 4 2013-03-11 $50.00 2013-01-15
Maintenance Fee - Application - New Act 5 2014-03-10 $100.00 2014-02-19
Request for Examination $400.00 2014-02-28
Maintenance Fee - Application - New Act 6 2015-03-10 $100.00 2015-02-13
Maintenance Fee - Application - New Act 7 2016-03-10 $100.00 2016-02-04
Maintenance Fee - Application - New Act 8 2017-03-10 $100.00 2017-01-16
Final Fee $150.00 2017-10-06
Maintenance Fee - Patent - New Act 9 2018-03-12 $100.00 2018-02-27
Maintenance Fee - Patent - New Act 10 2019-03-11 $125.00 2019-02-27
Maintenance Fee - Patent - New Act 11 2020-03-10 $125.00 2020-02-10
Maintenance Fee - Patent - New Act 12 2021-03-10 $125.00 2020-11-16
Maintenance Fee - Patent - New Act 13 2022-03-10 $125.00 2021-11-10
Maintenance Fee - Patent - New Act 14 2023-03-10 $125.00 2023-02-22
Maintenance Fee - Patent - New Act 15 2024-03-11 $253.00 2024-02-26
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
FONCLOUD INC.
Past Owners on Record
BERGER, SHAI
BIGUE, JASON P.
PULTZ, MICHAEL
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Office Letter 2022-05-17 2 185
Abstract 2010-08-24 2 63
Claims 2010-08-24 3 84
Drawings 2010-08-24 6 66
Description 2010-08-24 9 410
Representative Drawing 2010-08-24 1 8
Cover Page 2010-11-29 1 34
Claims 2016-02-18 5 186
Claims 2016-03-07 10 379
Claims 2016-12-22 7 317
Final Fee 2017-10-06 2 63
Representative Drawing 2017-10-20 1 6
Cover Page 2017-10-20 1 34
PCT 2010-08-24 6 243
Assignment 2010-08-24 2 80
Correspondence 2010-10-06 1 26
Fees 2010-11-09 2 58
Assignment 2010-11-09 4 146
Correspondence 2010-11-09 3 73
Office Letter 2016-02-11 1 23
Prosecution-Amendment 2014-02-28 1 44
Examiner Requisition 2015-08-18 3 224
Examiner Requisition 2016-06-22 3 196
Modification to the Applicant-Inventor 2016-11-28 2 67
Assignment 2016-01-29 2 58
Amendment 2016-02-18 18 602
Amendment 2016-03-07 26 916
Modification to the Applicant-Inventor 2016-06-01 4 75
Correspondence 2016-08-16 3 70
Office Letter 2016-09-09 1 20
Office Letter 2016-09-09 1 23
Correspondence 2016-10-07 1 24
Office Letter 2016-12-12 1 21
Amendment 2016-12-22 19 753